Connect a Slack app with a bot token, send to a channel or to a user by ID or email, use Block Kit, reply in threads, and update messages you already sent.
Choose “From scratch”, name your app, and select your development workspace.
Under “OAuth & Permissions”, add these Bot Token Scopes: chat:write, im:write, users:read, users:read.email.
Click “Install App to Workspace” and authorize.
Copy the Bot User OAuth Access Token (starts with xoxb-).
Slack OAuth Scopes
3
Design a Slack notification template
Go to Content → Templates in Courier and create a new template.
Select Slack from your integrations.
In the sidebar, click the new Slack block to open the Slack template editor.
Add your message content.
4
Send a test message
Click Preview, then Create Test Event.
Enter your bot token in the Access Token field.
Click Send. Your message appears in Slack.
Profile requirements
Slack addresses the recipient by channel, user id, or email, so the profile you send to needs a slack object holding an access_token and one target. Store both once with POST /profiles/{user_id}, which merges into the profile and creates it if it doesn’t exist:
Channel
User id
Email
The channel id, not its name. access_token is the bot token from your Slack app. It sits on the profile beside the target.
With Courier MCP, save the Slack user id UEFNTF6QL and my bot token on user_123.
Slack resolves the address to a user, then direct-messages them. access_token is the bot token from your Slack app. It sits on the profile beside the target.
With Courier MCP, save the Slack email sarah@acme-corp.com and my bot token on user_123.
Order of precedence. Set more than one of channel, user_id, or email and Courier uses them in that order.
Then send to user_id and Courier resolves the address.For a one-off with no stored profile, pass it inline instead: "to": { "slack": { "access_token": "xoxb-xxxxx", "channel": "CL2MR6HEX" } }.
Send by user id
The call in every language, and the rest of the profile object.
Send to a recipient
Send to user id
Send to slack
Courier reads slack off the saved profile, so preferences apply and the value can change without touching this code.
With Courier MCP, send my template to sarah@acme-corp.com on Slack.
Overrides
How overrides work covers the two levels and which one wins.You can override the payload sent to Slack’s chat.postMessage using providers.slack.override.body. This is useful for advanced formatting, interactivity, and threading.
With Courier MCP, send my template to user_123 as a reply in an existing Slack thread.
Mentioning users
Mention a user in your message using <@USER_ID> syntax in your template:
Hello <@UEFNTF6QL>, you have a new notification!
You can also use variables for dynamic mentions.
Preventing unwanted mentions
Slack automatically parses text for @name patterns and turns them into mentions. If your message content includes text that resembles a mention but shouldn’t trigger one, set verbatim: true on the Block Kit text object to disable this parsing.Courier’s standard template blocks (text, quote, etc.) don’t expose the verbatim flag. To use it, either pass raw Block Kit JSON via providers.slack.override.body.blocks or use a Jsonnet block in Design Studio:
{ "type": "section", "text": { "type": "mrkdwn", "text": ">>> Message from @jennifer about the deployment", "verbatim": true }}
Slash command responses
If responding to a Slash Command, use the response_url as an incoming webhook:
To update a previously sent Slack message, set a “replacement key” (usually ts) in your notification template’s Slack channel settings. Courier will use this key to update the message instead of posting a new one.
Delivery tracking
When Courier sends a Slack message via Bot OAuth (chat.postMessage), it captures Slack’s ts (message timestamp identifier) and channel (conversation ID) from the API response. You can use these values to thread replies, update messages, or link back to the original Slack message.
Slack conversation ID where the message was posted.
providers[].channel
Courier routing metadata (template and channel key). Not the Slack channel ID.
Slack messages are marked as DELIVERED immediately after sending because Slack’s API confirms delivery synchronously. The delivered and sent timestamps will be very close together.
Incoming Webhook sends carry no reference data, since Slack’s Incoming Webhook API doesn’t return ts or channel in its response.
Troubleshooting
Missing or incorrect Slack scopes:
Double-check your app has all required scopes (chat:write, im:write, users:read, users:read.email, and chat:write.public for channels).
Reinstall your Slack app after updating scopes.
Bot not invited to channel:
Make sure your Slack app/bot is a member of the channel you want to message.
Invalid or missing tokens:
Ensure you’re using the correct Bot User OAuth Access Token (starts with xoxb-).
Double-check the email, user_id, or channel ID. For channels, copy the ID from the Slack URL.
Message truncated:
Slack blocks limit the characters in a single section to 3k characters. Courier automatically truncates Slack messages over 3k characters by removing escape and formatting characters that Slack adds after you submit the block.