Skip to main content

Universal Webhook Trigger

The universal webhook trigger can be used to invoke a flow from any service that can send an HTTP request to a custom URL. Each flow that begins with a universal webhook trigger has its own uniquely generated webhook URL, and sending HTTP requests to that webhook URL causes the flow to execute. Each of your customers' instances' flows have their own webhook URL by default (though you can change that with Endpoint Configuration).

The universal webhook trigger is handy in many situations. To name a few:

  • A third-party API may support webhooks, but a connector does not have a dedicated trigger for the webhook events you're interested in. A flow that starts with the universal trigger can receive requests from any third-party app for any event.
  • You can implement webhooks in your own application. Your webhooks can invoke a universal webhook trigger, allowing you to send data from your app to your customers' third-party apps in real time.
  • Your frontend app can make synchronous requests to a flow with a universal webhook trigger in order to fetch data from a third-party in real time.

When should I build a custom webhook trigger?​

The universal webhook trigger is handy if the party calling the trigger sends a JSON or form data payload and expects a generic HTTP 200 response.

If the third-party you're working with requires a custom response (like a challenge code), if they send atypical payloads (like XML or YAML that needs to be parsed first) or if they secure requests by signing payloads with HMAC, you may need to wrap custom third-party logic in a custom trigger.