Aydrian Howard
September 16, 2020

Table of contents
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:
Be sure to Like the video and Subscribe to our YouTube 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.
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.
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

How Product Teams Build, Test and Ship Multichannel Notifications in Design Studio
Product teams need to build, test, and ship notifications across multiple channels without filing an engineering ticket every time. Courier's Design Studio is the workspace for that: a template builder, visual channel routing, omnichannel testing, and publishing in one place. This post walks through the traditional template designer paradigm, how it splits effort across too many tools, and outlines a path for product and growth teams to ship transactional, product, and marketing notifications from a single workspace.
By Kyle Seyler
March 12, 2026

EU Data Residency for Notifications: What Engineering Teams Need to Know
Courier supports EU data residency through a dedicated datacenter in AWS EU-West-1 (Ireland), with full API feature parity, same-workspace dual-region access, built-in GDPR deletion endpoints, and localization support for multilingual notifications. Engineering teams can switch to EU hosting by changing a single base URL with no workspace migration or downtime required.
By Kyle Seyler
March 09, 2026

Customer Engagement Platforms Are Splintered. Message Orchestration Is the Fix
Customer engagement platforms are splintered. Some are built for campaigns, others for support automation, and others treat messaging as a transactional delivery problem. The result is collisions, blind spots, and message fatigue. The highest-leverage fix is solving the lifecycle-to-product and transactional vector with a message orchestration layer: one system that routes, suppresses, prioritizes, and observes messages across channels. Think air traffic control for user communications.
By Kyle Seyler
March 03, 2026
© 2026 Courier. All rights reserved.