Iterable sends a webhook for the subscriber and campaign events you choose. FlowMattic catches it, decides which Slack channel or person should hear about it, and posts a readable message instead of raw JSON. For lifecycle and CRM marketers who want campaign activity and deliverability warnings in the channels they already use.
1 trigger 14 actions 6 example workflows 2 ready-made templates Unlimited runs
When this happens in Iterable1 trigger
Do this in Slack14 actions
1. TriggerSetup Webhook2. ActionSend Channel MessageWhen Iterable fires Setup Webhook, FlowMattic runs Send Channel Message in Slack with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templateEach event you enabled in Iterable posts with the campaign, email and event type, so the lifecycle team sees activity without opening a report.
Setup WebhookSend Channel Message
View the template One webhook can carry several event types. A Router sends campaign activity to marketing and subscription changes to the CRM team, so neither channel fills with the other's noise.
Setup WebhookRouterSend Channel Message
A Filter keeps only unsubscribe and complaint events and posts them to a private channel, so the person who looks after sender reputation sees problems early.
Setup WebhookFilterSend Private Channel Message
Iterable payloads can hold nested data fields. JSON Parser pulls out the values you want, such as campaign name or template, so the message reads cleanly.
Setup WebhookJSON ParserSend Channel Message
A Lookup Table maps the campaign ID to its owner's email, Find User by Email finds them in Slack, and the event arrives as a direct message.
Setup WebhookLookup TableFind User by EmailSend Direct Message
Date/Time Formatter turns Iterable's timestamp into a local date and time, so a message about a send reads the way the team talks about schedules.
Setup WebhookDate/Time FormatterSend Channel Message
At the end, the Iterable events you choose post to a Slack channel as readable messages.
Under Connects in FlowMattic, add the Slack workspace your marketing team uses.
Create a workflow with Iterable and Setup Webhook, copy the workflow's webhook address and add it as a webhook in Iterable.
In Iterable, enable only the events you want in Slack, then cause one so FlowMattic captures a sample.
Add Slack Send Channel Message, map the event type, email and campaign into the text, test it and switch the workflow on.
1. Trigger in Iterable
Setup Webhook
2. Action in Slack
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
| From Iterable | To Slack |
|---|---|
| Event name | Message: what happened |
| Message: subscriber | |
| Campaign ID | Message: campaign |
| Created at | Message: time |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Iterable and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Campaign and subscriber events become short Slack messages, so the team talks about results where it plans the next send.
Unsubscribe and complaint spikes reach the person who looks after deliverability, rather than a general channel.
FlowMattic runs on your WordPress site with unlimited runs, so a large send that fires many events costs nothing extra.
Create a FlowMattic workflow with the Iterable Setup Webhook trigger, add the workflow's webhook address as a webhook in Iterable with the events you want, capture a sample, then add Slack Send Channel Message.
Any event you enable on the Iterable webhook reaches the workflow. A Filter or Router on the event type then decides which ones are posted and where.
Yes. A Router after the trigger checks the event type and has one path per channel, for example campaign activity to marketing and unsubscribes to a private deliverability channel.
Some values arrive nested. Add JSON Parser after the trigger to pull out the fields you need, then map those into the Slack text instead of the whole object.
It can if every open and click is enabled. Keep high-volume events off the webhook, or filter them out, and post only the events someone acts on.
Did not find your answer? You can browse the help center or ask us directly.
Slack and Google Sheets149 shared templates
Slack and Airtable44 shared templates
Slack and Fluent Forms42 shared templates
Slack and FluentCRM35 shared templates
Slack and ClickUp28 shared templates
Slack and Fluent Support21 shared templates
Slack and WooCommerce18 shared templates
Slack and Notion17 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Iterable integration 1.0.0, Slack integration 1.0.
