Send a Slack alert when a Netcore Cloud webhook event is received
When Netcore Cloud sends a webhook for an event you have set it to report, this workflow posts a message in a Slack channel, so your team sees campaign activity without opening the Netcore Cloud dashboard.
Netcore Cloud
Slack2 steps Setup ~5 min Used on 2.8k sites Free to import
What this workflow does
Netcore Cloud can report events from your campaigns by webhook, but those reports are only useful if someone sees them. A Slack channel your marketing or ops team already watches is a natural place to surface them. This workflow forwards each event Netcore Cloud sends into that channel.
The Netcore Cloud trigger, Setup Webhooks, fires when a response is received related to an event you specify. In Netcore Cloud you point the webhook at the URL FlowMattic gives you and choose which events it reports. Each delivery starts one run, and its values become available to map.
The Slack step posts a message to the public channel you select. Write the text yourself and add the event values that help someone act, for example the recipient or event type if your test payload includes them. Without a Filter, every event Netcore Cloud delivers becomes a Slack message, so pick the reported events with care. Task History logs each run with the data Netcore Cloud sent.
Watch bounces during a big send
If your Netcore Cloud webhook reports bounces, the email team sees each one in Slack while the campaign is still going out.
Flag spam complaints quickly
If you set Netcore Cloud to report complaint events, each one appears in a Slack channel where the deliverability owner can look into it.
Shared view of campaign activity
A small marketing team without dashboard access for everyone follows the events Netcore Cloud reports in one Slack channel.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Netcore Cloud Setup WebhooksStarts a run each time Netcore Cloud sends a webhook for an event you set it to report. The values in that delivery are passed on to the Slack message.
- Slack Send Channel Message
Puts a new message in one public Slack channel of your choosing. Compose the text and drop in values from the Netcore Cloud event, then connect your Slack workspace on import.
What you need
- FlowMatticCore
- Netcore Cloud AccountAccount
- Slack AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Busy campaigns can send many events. Add a Filter after the trigger so only the event types you care about reach Slack, using the value your test run shows for the event.
- Alerts headed for a private Slack channel need the Send Private Channel Message action in place of this one, and Send Direct Message suits a single person.
- Send a test event from Netcore Cloud after import so FlowMattic captures a real payload to build the Slack message from.
Questions about this workflow
Which Netcore Cloud events reach Slack?
Whichever events you set the Netcore Cloud webhook to report. Each one that reaches the FlowMattic URL starts a run and posts a message.
Can the Netcore Cloud alert go to a private Slack channel?
The imported Send Channel Message step isn't meant for that. Slack in FlowMattic has a separate Send Private Channel Message action; swap it in for a private channel.
Will a large Netcore Cloud campaign flood the Slack channel?
It can, because every event delivered becomes a message. Report fewer event types in Netcore Cloud or add a Filter to keep the channel readable.
Can I see what Netcore Cloud sent for a past alert?
Yes. Task History keeps each run, including the data received from Netcore Cloud and the message posted to Slack.
More Notifications & Alerts workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted