If you're not familiar with webhooks, they may sound intimidating. But they're actually pretty simple: webhooks are a way for apps to "talk" to each other. Instead of manually updating information across all of the apps your company uses, you can connect those apps to Iterable with webhooks so that they automatically update as soon as something new happens in Iterable.
You can set up your webhooks to send relevant information in each request—like a campaign or event name, a user's email address, or authentication credentials.
To learn more about webhooks and how they can make things easier for you, check out this blog post from our friends at Zapier.
All of the webhooks you set up in Iterable must use HTTPS-based URLs. Starting June 30th, 2022, webhooks that rely on HTTP URLs will fail. To learn more, see the Webhook HTTPS Update release notes.
Using webhooks in Iterable
There are two ways you can use webhooks in Iterable:
System webhooks can help you monitor what's going on in your Iterable project. You can use system webhooks to have Iterable call a webhook every time an event occurs (like an email send, a push notification open, an SMS bounce, or a list unsubscribe).
Journey webhooks let you connect other apps and services to your Iterable journeys. You can use journey webhooks to update a user's Iterable profile, send data to Segment, set up direct mail sends with Inkit, trigger an action in Zapier, launch NPS surveys with Delighted, and more.
Article is closed for comments.