Emarsys runs your email, SMS and lifecycle campaigns, and can send its events out by webhook. FlowMattic catches those events and posts them to Slack in a form people can read: the event type, the contact and the campaign. CRM and marketing teams see the Emarsys activity they choose without reading raw payloads or logging in to the platform.
1 trigger14 actions5 example workflows2 ready-made templatesUnlimited runs
Try a pairing
When this happens in Emarsys1 trigger
Do this in Slack14 actions
1. TriggerSetup Webhook
2. ActionSend Channel Message
When Emarsys 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
Emarsys and Slack workflows you can build
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 template
Post each Emarsys webhook event to the marketing channel
Whichever events you set up in Emarsys arrive in the marketing channel as a short message, which is the quickest way to see what the webhook sends before building more.
One Emarsys webhook can carry several event types. A Router reads the type, so campaign events go to marketing and contact changes go to the CRM team's channel.
Setup Webhook→Router→Send Channel Message
Pick the useful fields out of nested payloads
Emarsys payloads can nest the contact and campaign details. JSON Parser pulls out the fields you need so the Slack message shows names instead of a block of raw data.
Setup Webhook→JSON Parser→Send Channel Message
Message the campaign owner about their own campaigns
A Lookup Table maps each campaign to its owner's email. Slack finds that person and sends a direct message, so owners hear about their campaigns without following a busy channel.
Setup Webhook→Lookup Table→Find User by Email→Send Direct Message
Keep a searchable log and post only the exceptions
Every event is stored in WP Tables on your site. A Filter then passes only the event types you treat as problems, such as failed sends, to a private channel for the CRM team.
Post each Emarsys webhook event to the marketing channelTemplate
1. Trigger in Emarsys
Setup Webhook
2. Action in Slack
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
From Emarsys
To Slack
Event type
Message: what happened
Contact email
Message: contact
Campaign name
Message: campaign
Timestamp
Message: time
Built on the FlowMattic canvas. Test each step with real data, then switch the workflow on.
Triggers and actions in this pair
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Good to know
The events and fields depend on what you subscribe to in Emarsys, so the mapping is an example. Capture one event of each type before building a Router on them.
High-volume events such as opens can arrive in large numbers after a big send. Store them with WP Tables or filter them, rather than posting each one to a channel.
Send Channel MessagePost or Schedule a new message to a specific #channel
Add ReminderAdds a reminder for the user
Create ChannelCreates a new channel
List All ChannelsRetrieve list of all channels
Set Channel TopicSets the topic on a selected channel
Set StatusSets your Slack status to the given text and emoji
Invite User To ChannelInvite an existing User to an existing Channel. You must be a member of the channel to invite someone to it
Find User by EmailFinds a user by matching against their email instead of their username
Find User by IDFinds a user by their ID.
Send Direct MessageSend a direct message to a user or yourself from the Slackbot. Can also schedule a message for later
Send Private Channel MessagePost a new message to a private channel you choose. Can also schedule a message for later
Update ProfileUpdate basic profile fields such as name or title
Find MessageFinds a Slack message using the Slack Search feature
Upload FileUpload file to your slack workplace
Why run this pair with FlowMattic
Emarsys and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Webhook data people can read
Raw Emarsys payloads become short Slack messages with the event, contact and campaign, so non-technical teams can follow them.
One trigger, many routes
A single webhook trigger can feed different channels and owners, so adding a new event type is one more Router path.
Customer events on your own server
FlowMattic runs on your WordPress site with unlimited runs, so campaign spikes do not change what you pay.
Common questions
How do I send Emarsys events to Slack?
Create a FlowMattic workflow with the Emarsys Setup Webhook trigger, add its address as a webhook in Emarsys for the events you want, then add Slack's Send Channel Message. Capture a test event, map the fields and switch the workflow on.
Which Emarsys events can I use?
The trigger receives the events you subscribe the webhook to in Emarsys. Use a Router or Filter on the event type when one webhook carries several kinds of event.
The payload is hard to read. What can I do?
Add a JSON Parser step after the trigger to pull out nested fields such as the contact's email or the campaign name, then map those fields into the Slack message.
Can I update a CRM from the same events?
Yes. Add your CRM's step, for example ActiveCampaign Create or Update Contact, before the Slack message, so the contact is updated and the team is told in one workflow.
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. Emarsys integration 1.0.0, Slack integration 1.0.