Using webhooks in workflows

  • The webhooks used in workflows are completely separate from the webhooks sent for an OAuth app that would be managed through the Webhooks API. For more details about that type of webhook, please see the documentation here.
  • Webhook actions are only available with an Enterprise subscription. See this article for more details.

For more details on setting up a webhook action in a workflow, see this knowledge article.

When the webhook action is set to the POST method, the webhook will POST the data for the contact going through the workflow. The data will be the exact same data you'd get when pulling that contact using the Contacts API. Note: Webhooks set to the GET method will not send any data for the contact, it will simply hit the specified URL.

Webhooks follow these rules for connecting and retrying requests:

  • Workflows waits up to 3 seconds to connect to a tcp socket, if this fails we will retry.
  • Workflows waits up to 30 seconds for a response (aka request timeout).
  • Workflows will not retry after receiving 4XX or 5XX series response status codes.
    • One exception to this rule is 429 rate limit errors; workflows will automatically retry after receiving a 429 response, and will respect the Retry-After header if present.
  • Workflows will issue webhook attempts at up to 20 requests per second.