Slack setup
Connect SendBeam to Slack: what you need, the steps, and the code.
Native
Sending paused, an automation that cannot finish, a domain that failed its checks — the messages worth interrupting someone for, posted straight into a Slack channel with no automation tool in between.
Before you start
- An account with Slack
Set it up
- Create an incoming webhook in Slack. In Slack, go to Apps → Incoming Webhooks → Add to Slack, pick the channel the alerts should land in, and copy the URL it gives you — it looks like
hooks.slack.com/services/.... That URL is a credential on its own: anyone holding it can post to the channel, and it carries no other authentication, so treat it the way you would treat a password. - Add it in SendBeam. Settings → Webhooks → Add endpoint. Choose Slack, paste the URL, and tick the events worth interrupting someone for.
- Send a test event. The button beside the endpoint posts a message marked as a test, so you can confirm it arrives before anything real depends on it.
Code
Directly: SendBeam → a Slack channel
Settings → Webhooks
1. In Slack: Apps → Incoming Webhooks → Add to Slack
Choose the channel, copy the URL (hooks.slack.com/services/...)
2. In SendBeam: Settings → Webhooks → Add endpoint
Where A Slack channel
Endpoint URL the URL Slack gave you
Events Sending paused, Sending resumed,
Delivery results deteriorating,
Automation failed, Campaign sent,
Domain verified, Domain failed
3. Send test event — a message appears in the channel, marked as a test
Each message names its workspace, so several workspaces can point at one channel. Delivery retries on failure and the endpoint turns itself off if the URL stops working, with the reason on the Deliveries page.
In n8n: SendBeam events to a Slack channel
n8n workflow
1. SendBeam Trigger
Events Contact Created, Contact Unsubscribed, Form Submitted
2. Slack → Message → Send
Channel #signups
Text {{ $json.event }}: {{ $json.data.contact.email }}
Publishing the workflow sets up the SendBeam webhook for you. Form submissions carry the address as data.email rather than data.contact.email.
In Make: SendBeam webhook to Slack
Make scenario
Module 1: Webhooks → Custom webhook (copy its address)
In SendBeam: Settings → Webhooks → Add endpoint
paste the address, choose contact.created
Module 2: the Slack module that sends a message to a channel
Text: New subscriber: {{1.data.contact.email}}
Run the scenario once and use Send test event on the endpoint in SendBeam, so Make learns the payload’s fields.
In Zapier: SendBeam webhook to Slack
Zap
Trigger Webhooks by Zapier, catching a hook (copy its URL)
In SendBeam: Settings → Webhooks → Add endpoint
paste the URL, choose contact.created
Action Slack's action for sending a channel message
Text: New subscriber: map Data Contact Email
Webhooks by Zapier is available on Zapier’s paid plans. Send test event in SendBeam gives Zapier a sample with the same fields a real event has.
Things to know
- A Slack channel carries the operational events only — pauses, resumes, deliverability warnings, automation failures, campaign sends and domain results. For contact-level events use one of the automation routes below; a message per subscriber is a channel nobody reads.
- Choose only the events the channel needs; every subscriber on a busy list is a lot of messages.
- Test events carry test: true in data, so a workflow can skip them. A direct Slack test message says so in the text.
- The full list of events is in the webhooks documentation.
Stuck, or found a gap? Ask in the community — questions, tips and every release note, with this page as the source of truth.