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

investigation workflow
CourierEngineering

How We Investigate Support Tickets at Courier

Courier's support team resolves complex issues 4X faster using parallel investigation. Here's how it works: when a ticket comes in, an AI agent starts exploring the codebase while the support engineer examines actual customer data. The agent traces code paths and searches past investigations. The human reads event logs and forms hypotheses based on real state. Running both simultaneously catches mismatches fast—the agent sees what could cause a problem, the human sees what actually happened. This post breaks down the workflow, tools, and documentation structure that makes it repeatable.

By Thomas Schiavone

December 18, 2025

Best Notification Messages - Courier
Notifications LandscapeCourier

Top 20 Notification Examples That Actually Drive Engagement

Explore 20 stellar notification examples from industry leaders like Rippling, Slack, FedEx, Crocs, Miro, Trustpilot, OpenTable, and BambooHR that actually drive engagement. From payday celebrations to healthcare reminders, these patterns showcase what makes notifications effective across email, SMS, push, and in-app channels. Courier's enterprise platform enables intelligent routing, multi-channel orchestration, and universal inbox integration to implement these proven patterns at scale.

By Kyle Seyler

September 25, 2025

Courier MCP Server Video Demo
CourierEngineeringProduct Management

Video Guide: Courier MCP + AI Coding (Cursor)

Building notifications into your app just got dramatically easier. Courier's new MCP server brings AI-powered notification assistance directly to your IDE, so you can integrate, test, and manage notifications without ever leaving your workspace. Model Context Protocol servers give AI agents deterministic functionality instead of guessing. Connect your AI assistant directly to Courier's platform, get smart installation guidance, send messages with natural language, and manage users safely—all through Cursor, Claude Code, VS Code, and more.

By Kyle Seyler

September 04, 2025

Multichannel Notifications Platform for SaaS

Products

Platform

Integrations

Customers

Blog

API Status

Subprocessors


© 2025 Courier. All rights reserved.