Aydrian Howard
September 30, 2020

Table of contents
Check out the video below to watch us:
Be sure to Like the video and Subscribe to our YouTube channel.
During the stream we used the newly updated Courier Node.js SDK to work with our lists. During this we ran into a few issues and shortly after the stream ended, we released a patch to address them. The following code uses v1.6.1 of the SDK which can be installed using yarn or npm.
Copied!
> npm install @trycourier/courier
A list can be created ahead of time or when a recipient subscribes to a list that doesn't exist. We created a couple lists using both methods. List IDs are composed of up to 4 parts separated by a dot. For our example, we are creating a list for Courier Live Alerts so we'll use courier.devrel.live. You can learn more about List ID Pattern guidelines in our help center.
Copied!
const { CourierClient } = require("@trycourier/courier");const courier = CourierClient({ authorizationToken: "<AUTH_TOKEN>" });const listId = "courier.devrel.live";const main = async () => {await courier.lists.put(listId, {name: "Weekly Product Updates"});const list = await courier.lists.get(listId);console.log(list);};main();
Because the list.put method doesn't return anything, I also added a call to the list.get method to show the list had been added.
To add a recipient to a list, you first need to make sure they have a Profile stored in Courier. Here is how you would add a new recipient to a list that will be created on the fly.
Copied!
const { CourierClient } = require("@trycourier/courier");const courier = CourierClient({ authorizationToken: "<AUTH_TOKEN>" });const listId = "courier.product.live";const main = async () => {const { status } = await courier.mergeProfile({recipientId: "CUSTOMER94107",profile: {email: "customer@company.com",given_name: "Customer",custom: {twitter: "https://twitter.com/company"}}});console.log(status);await courier.lists.subscribe(listId, "CUSTOMER94107");const { results } = await courier.lists.findByRecipientId("CUSTOMER94107");console.table(results);};main();
Here we created a new recipient profile using the Profiles API and then subscribed them to a new list. Because the lists.subscribe method doesn't return anything, I also added a call to the list.findByRecipientId method to show that the recipient was added to the newly created list.
Now that we have a couple lists, we can send a notification to them. We can target a specific list by sending using its List ID
Copied!
const { CourierClient } = require("@trycourier/courier");const courier = CourierClient({ authorizationToken: "<AUTH_TOKEN>" });const listId = "courier.devrel.live";const data = {title:"Courier Live: First Look at Notifying Multiple Recipients using Lists",hosts: [{name: "Aydrian",twitter: "https://twitter.com/itsaydrian"},{name: "Danny",twitter: "https://twitter.com/DannyDouglass"}]};const main = async () => {try {const { messageId } = await courier.lists.send({event: "COURIER_LIVE_ALERT",list: listId,data});console.log(messageId);} catch (e) {console.log(e.message);}};main();
We can target multiple lists by using a pattern. We could send to all subscribers under courier by using the pattern courier. or we could target all the live lists with the pattern courier.*.live. You can learn more about patterns in our help center. Let's send to every list under courier.
Copied!
const { CourierClient } = require("@trycourier/courier");const courier = CourierClient({ authorizationToken: "<AUTH_TOKEN>" });const pattern = "courier.**";const data = {title:"Courier Live: First Look at Notifying Multiple Recipients using Lists",hosts: [{name: "Aydrian",twitter: "https://twitter.com/itsaydrian"},{name: "Danny",twitter: "https://twitter.com/DannyDouglass"}]};const main = async () => {try {const { messageId } = await courier.lists.send({event: "COURIER_LIVE_ALERT",pattern,data});console.log(messageId);} catch (e) {console.log(e.message);}};main();
Courier will handle gathering and de-duping all the recipients that satisfy the pattern. Check out the Lists API Reference documentation to learn about all that can be done with lists.
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

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

Customer Engagement Platform vs CRM: Key Differences Explained
A CRM stores customer data: contacts, purchases, support tickets, and pipeline. It answers "who are our customers?" A customer engagement platform (CEP) orchestrates communication across email, push, SMS, in-app, and chat. It answers "what should we tell them next?" CRMs focus on historical records. CEPs process real-time behavior and trigger messages based on actions. Most teams need both, plus a third layer: notification infrastructure for reliable multi-channel delivery. Courier bridges CEP and infrastructure by combining routing, failover, and delivery tracking with engagement features like preference management, visual templates, and in-app notification centers.
By Kyle Seyler
January 07, 2026

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
© 2026 Courier. All rights reserved.