Send Data to Other Apps with the Custom Webhook Action

The Custom Webhook action lets a workflow push information to any web address you choose. Use it to notify another system, create a record in a third-party tool, or fetch data that you then use in later steps.

What you can configure

• URL: the endpoint that should receive the request.
• Method: POST, GET, PUT, or DELETE.
• Authorization: pick the type of credential the receiving service expects.
• Headers: extra request details such as content type or an API key.
• Query parameters: values added to the URL to filter or shape the response.
• Body data: a payload you build with merge fields, including values from an inbound webhook.

Set it up

1. Open a workflow and click + to add an action.
2. Choose Custom Webhook.
3. Enter the URL and select the Method.
4. Choose an Authorization option if the service needs one.
5. Add any Headers and Query Parameters.
6. Compose the body. Start typing a merge field name and use the autocomplete suggestions.
7. Save and publish.

Handling errors

The action succeeds only when the receiving service responds successfully. If it returns an error, the contact's execution shows the step as failed and either skips it or retries with increasing delays. The action fires as soon as a contact reaches it, so if many contacts arrive together, make sure the other service can handle the volume. A short Wait between steps or staggered enrolment prevents rate limit errors.

Test before going live

Send a request to a test endpoint first, review the response in the execution log, and only then point the action at production.

Good to know: Never paste secret keys into the message body of a widely shared workflow; use the Authorization section so credentials stay out of the content.