Webhooks Overview

To send data to other applications, Iterable uses webhooks: HTTP requests to external URLs. Iterable can make webhook requests in response to system events (an email open or click, a push notification open, etc.) or as part of a workflow.

The URL associated with a webhook must be hosted by your organization or a third-party application. When making a webhook request, Iterable can pass along relevant information such as authentication credentials, a campaign name, an event name, or an email address. The specific data sent from Iterable to the webhook URL depends on the webhook's configuration in Iterable.

The following guides describe the two types of webhooks that Iterable supports: system webhooks and worfklow webhooks.

# System webhooks

To have Iterable call a webhook for each occurrence of an event such as an email blast send, a push notification open, an SMS bounce, or an email unsubscribe, use a system webhook.

# Workflow webhooks

To configure Iterable to call a webhook as part of a workflow, use a workflow webhook. Workflow webhooks allow external applications to participate in Iterable workflows.