Overview
What Slack is
Slack is the messaging tool where B2B teams spend their workday, so it is a place your users already want to receive updates from the products they use.
Courier adds Slack as another channel in your existing notification system, with the same templates, routing, and preferences as email, SMS, push, and inbox. There is no separate Slack integration to build.
You need a Courier account and a Slack app with a bot token, so your users can connect their Slack.
Why Courier
What you get with Slack + Courier
Let users choose Slack
Each user picks where they get a given notification, email or Slack, and Courier routes to their choice automatically.
Deliver messages users can act on
Send rich Slack messages built with Block Kit, so a notification can carry buttons and structure users act on in the conversation.
Add Slack to any journey
Drop Slack into an existing onboarding, reminder, or digest flow with delays and branching, no new code in your app.
One template, every channel
Write a notification once in Courier's editor and it renders to Slack alongside email, SMS, push, and inbox.
Add an in-app inbox too
Pair Slack with a drop-in inbox for web and mobile (JavaScript, React, iOS, Android, Flutter, React Native), so users also see messages inside your product.
Same API as your other channels
Slack joins your stack from the same Send API and templates you already use, so there is nothing new to wire up.
Use cases
What teams build with it
Setup
Connect it in minutes
An admin adds Slack once on the Integrations page in Courier. Once connected, anyone on your team can deliver notifications to Slack from any notification, alongside every other channel.
FAQ
Frequently asked questions
Can I use Slack with Courier?
Yes. Courier supports Slack as a direct-message provider, so you can deliver notifications to users inside Slack through the Send API and Journeys, not only through email or push.
Can I send notifications to my users on Slack?
Yes. Courier delivers to a recipient's Slack DM or a specific channel, so end users receive product notifications like comments, approvals, or mentions in Slack from the same notification you send to your other channels.
What do I need to connect Slack to Courier?
A Slack app with a Bot User OAuth token that starts with xoxb-, plus scopes such as chat:write, im:write, and users:read. Create the app, install it to your workspace, then add the bot token in Courier's Slack provider settings.
How does Courier know which Slack user to notify?
Store a slack object on the recipient's Courier profile with the bot access_token and one target: channel, user_id, or email. If you set more than one, Courier resolves them in the order channel, then user_id, then email.
Can I send rich Slack messages instead of just plain text?
Yes. Courier sends plain text and Slack Block Kit layouts, so notifications can include header and section blocks, buttons, and markdown. Pass raw blocks via providers.slack.override.body.blocks or build them in the template designer.
Does Courier confirm when a Slack message is delivered?
Yes. On a successful send Courier marks the message DELIVERED and captures Slack's ts timestamp and channel id. Those values also let you post threaded replies with thread_ts and update an existing message.
Is Slack just for internal alerts with Courier?
No. Slack is often used for internal ops alerts, but with Courier it doubles as a customer-facing channel, delivering your product's notifications to users alongside email, SMS, push, and the in-app Courier Inbox.
More
