Nick Gottlieb
May 25, 2022

We’re excited to announce a powerful new feature for the Courier platform: Courier Automations. Courier Automations is a toolset that includes both an API and a visual builder that allows anyone to easily configure logic for notification workflows. Need to send a reminder to class attendees 10 minutes before the class starts? Need to page an on-call engineer on multiple channels until they respond? These use cases and more can be achieved quickly and easily with Automations.
As developers, notifications are the primary way that the applications we build communicate with our end-users and the use cases vary widely. Some use cases are very straightforward and simply require that a single message goes to a single user once. Many notifications however require more sophisticated orchestration in order to deliver the desired user experience. Most developers today end up building a separate service to manage this logic. This results in additional infrastructure and development overhead and often in a less than ideal end-user experience.
We built Automations so that developers can deliver the ideal notification experience without needing to build and maintain yet another service.
While today marks the official release of Automations, many of our customers are already using Automation to power key parts of their product experience.
The engineering team at LaunchDarkly, a feature management platform, uses Automations to define the logic for notifications associated with approvals for their customers' feature releases. Any time approval is requested or granted, an Automation is triggered to ensure all the relevant stakeholders are alerted. You can read more about their use case here.
Officevibe, which is an employee experience platform, regularly sends out Slack notifications on behalf of their customers asking employees to complete a brief survey. Their engineering team utilizes the Automations API to create lists of users for whom the Slack survey could not be delivered and send them an email survey instead.
For Yoga International, an online Yoga platform, it's essential that they deliver a seamless experience to their customers from the time they register for a live class through to the start of class. Their engineering team utilizes the Automations API to send timely reminders to class attendees for each live class that happens on their platform.
Let's build a meetings reminder that sends an email reminder 10 minutes before the meeting and a link to the meeting notes two hours after the meeting.
Design the Messages:


npm install node-fetchautomations object with an array of objects called stepsCopied!
"automation": {"steps": [{"action": "send","template": "template_id",}]},
Copied!
"automation": {"steps": [{"action": "send","template": "template_id_1"},{"action": "delay","duration": "130 minutes"},{"action": "send","template": "template_id_2"}]},
template_id_1 with the notification template from Step 3 of “Design the Message” and update template_id_2 with the notification template from Step 5 of “Design the Message”brand and recipient attributes with your preferred brand and recipient IDstemplate attributeCopied!
// Dependencies to install:// $ npm install node-fetch --saveconst fetch = require('node-fetch');const options = {method: 'POST',headers: {Accept: 'application/json','Content-Type': 'application/json',Authorization: 'Bearer replace-token'},body: JSON.stringify({"automation": {"steps": [{"action": "send","template": "template_id_1"},{"action": "delay","duration": "130 minutes"},{"action": "send","template": "template_id_2"}]},"brand": "W50NC77P524K14M5300PGPEK4JMJ","template": "EXAMPLE_NOTIFICATION","recipient": "8ec8c99a-c5f7-455b-9f60-8222b8a27056","data": {"name": "Jane Doe","age": 27},"profile": {"phone_number": "2025550125","email": "hello@example.com"}})};fetch('https://api.courier.com/automations/invoke', options).then(response => response.json()).then(response => console.log(response)).catch(err => console.error(err));
This example demonstrates integrating an API V2 notification send call (Step 5 of "Design the Message").


Copied!
{"action": "send","message": {"to": {"email": "example@email.com"},"content": {"title": "Meeting Notes","body": "Link to meeting notes: ..."}}}
This step can be done within the designer by following Step 3
Copied!
{"data": {},"profile": {"email": "example@email.com","name": "Your Name"}}

Sign up for a free Courier account to get started with Automations. Courier’s Free Tier includes Automations and up to 10,000 notifications per month.

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

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