Background: Why webhooks?
Webhooks is part of a larger platform offering: custom connectivity. While we have a strong list of triggers out of the box, user data shows that 44% of our users require custom connectivity to some extent. It is typically used to connect to proprietary or legacy apps.
Users use webhooks for time-sensitive use cases. These use cases require real-time triggering of workflows like requesting an outbound call to a lead downloading the company ebook.
- Users looking to build recipes with real-time triggers
- Available to all plans
Why we built it
Webhooks has been a key part of many customer use cases. In the last year alone, Workato saw more than 2.5x increase in the number of recipes using webhook triggers to enable real-time automation. This trend is expected to continue increasing exponentially. We want to make the user experience for this popular trigger the best out there.
How it works
This wizard takes the user through a guided flow to test and verify a webhook trigger. We take the information from this test to configure the metadata automatically.
What problems are solved for you?
Unlike other products in the iPaaS space, building a webhooks trigger can now take less than 5 mins (down from 15-30 minutes). Often, users will need to switch back and forth between the recipe and their app. Additionally, users need to learn/understand the webhooks metadata – what the webhook schema looks like, which HTTP method and data type to expect. Lastly, it is difficult to verify that a webhook trigger is configured correctly. Users needed to do end-to-end tests with active recipes.
- Simplify UX – users can verify if the webhook trigger works immediately.
- Reduce skill barrier and human error – wizard detects key information and uses it to configure the trigger automatically.