Blog
COURIER

Sending Notifications via Slack

Aydrian Howard

September 16, 2020

Courier Live Header

Table of contents

Slack as a Notification Channel

As a follow up to the Courier Live where Troy and I built the Pigeon Weather App, I went back and added support for sending the notification as a direct message in Slack. Adding this additional channel only required adding the Slack provider, designing the message, and updating our Glitch App to accept Slack profile information.

Check out the video below to watch me:

  • Add a Slack Channel to an existing notification
  • Create a Slack App and install it to a test workspace
  • Update the Pigeon Weather application to update Courier Profiles with Slack information
  • See the notification delivered via Slack DM

Be sure to Like the video and Subscribe to our YouTube channel.

Slack as a Notification Channel

Courier makes it easy to send notifications to a Slack channel or as a direct message to a Slack user. You can use your existing Slack App or create a new one, as long as it has the proper permissions granted via OAuth scopes. You can then send a notification by providing a slack object to the profile that includes the Slack App Bot User OAuth Access Token (bot token) and either the channel id, user id, or user email address.

Sending to a Slack Channel

To send to a Slack public or private channel, your Slack app must be granted the chat:write scope. Your Slack app must also be a member of the channel you're sending to. The recipient profile requires the bot token and channel id. This can be supplied to the send in the profile object, but I like to use the Profiles API to create a channel recipient profile.

Copied!

import { CourierClient } from "@trycourier/courier";
const courier = CourierClient({ authorizationToken: "<AUTH_TOKEN>" });
const { status: mergeStatus } = await courier.mergeProfile({
recipientId: "CHANNEL_GENERAL",
profile: {
slack: {
access_token: "xoxb-xxxxx",
channel: "CL2MR6HEX",
},
},
});
console.log(mergeStatus);

You can learn more about sending to public and private channels in our Slack documentation.

Sending a Direct Message

To send a direct message, in addition to the chat:write scope, your app will also need to be granted the im:write scope. For sending a direct message, you have a few options when setting up the recipient profile. You could use a Slack Button, the user's Slack user_id, or the email associated with the user's account like we did in our Pigeon Weather example. To simplify setting up a recipient profile for a Slack direct message, we added the shortcut to allow you to use the email address. This method does require that you add the users:read and users:read.email scopes because Courier will do the user_id lookup for you using the Slack API. Now you can either supply the profile information to the send or live above, use the Profiles API to add the Slack profile to your recipient's profile.

Copied!

import { CourierClient } from "@trycourier/courier";
const courier = CourierClient({ authorizationToken: "<AUTH_TOKEN>" });
const { status: mergeStatus } = await courier.mergeProfile({
recipientId: "STANPINES97009",
profile: {
slack: {
access_token: "xoxb-xxxxx",
email: "stan.pines@themysteryshack.com",
},
},
});
console.log(mergeStatus);

You can learn more about the different options for sending direct messages in our Slack documentation.

Feel free to remix our Pigeon Weather Glitch app and connect your Slack app to it and start sending Slack messages.  Then, check out our Jsonnet Courier Live to learn how to create messages using dynamic Block Kit elements.

Is there something you’d like to see us do using Courier? Let us know and it might be the subject of our next Courier Live. We stream a new Courier Live every Wednesday at noon Pacific. Follow us on Twitch to be notified when we go live.

-Aydrian

Similar resources

healthcare messaging
Notifications LandscapeCourier

The $5.9 Billion Rebuild: Why Healthcare Is Replacing Its Notification Infrastructure

The clinical alert and notification market will reach $5.9 billion by 2032, growing at 12.3% annually. That number represents hardware, software, and services combined. It also represents healthcare's admission that pagers and overhead speakers aren't enough anymore. Healthcare organizations are rebuilding how critical information moves through their systems. Regulatory pressure, workforce shortages, and value-based care economics are forcing the investment. The software layer is where outcomes are won or lost.

By Kyle Seyler

February 02, 2026

a guide for ai assisted development: Notification infrastructure
CourierNotifications LandscapeEngineering

Vibe Coding Notifications: How to Use Courier with Cursor or Claude Code

Courier's MCP server lets AI coding tools like Cursor and Claude Code interact directly with your notification infrastructure. Unlike Knock and Novu's MCP servers that focus on API operations, Courier's includes embedded installation guides for Node, Python, Flutter, React, and other platforms. When you prompt "add Courier to my app," your AI assistant pulls accurate setup instructions rather than relying on outdated training data. OneSignal's MCP is community-maintained, not official. Courier supports 50+ providers, native Slack/Teams integration, drop-in inbox and preference components, and a free tier of 10,000 notifications/month. Configure in Cursor with "url": "https://mcp.courier.com" and "headers": { "api_key": "YOUR_KEY" }.

By Kyle Seyler

January 22, 2026

b2b customer engagement guide
Notifications LandscapeCourier

The Complete Guide to B2B Customer Engagement

Courier provides the notification infrastructure layer for B2B customer engagement, routing messages across email, SMS, push, in-app, Slack, and Teams based on user preferences and product events. Unlike building notification systems in-house—which takes months of engineering time for features like multi-channel routing, preference management, and delivery tracking—Courier handles this infrastructure so product teams can focus on engagement strategy. B2B customer engagement requires multiple layers: notification infrastructure (Courier), customer data platforms (Segment), product analytics (Mixpanel/Amplitude), and channel-specific tools. Companies with strong engagement programs see 15-25% churn reduction. The key is connecting product events to customer communication at the right moment through the right channel, handling complexity like multiple users per account with different notification needs across work channels.

By Kyle Seyler

January 20, 2026

Multichannel Notifications Platform for SaaS

Products

Platform

Integrations

Customers

Blog

API Status

Subprocessors


© 2026 Courier. All rights reserved.