Courtney Chuang
January 27, 2021

Today, we’re excited to announce the release of Environments in Courier. You can now create, preview, and troubleshoot your notifications in a test environment before going live.
With support for two environments – Test and Production – you no longer have to worry about accidentally sending a notification to your users before you’re ready. Having an isolated test environment means you can safely debug your notifications, invite your team to make changes, and ensure your notifications work exactly as you intend before shipping to production.
Let’s take a look at what’s possible with Environments in Courier.
Both your test and production environments have two API keys: Draft and Published. Across the four API keys, you can easily and seamlessly map your development environments to your workflow in Courier. For example, you might use the Published key in the Test environment for testing and the Draft key in the Production environment for staging.

We designed Environments to make it simple and fast to migrate your notification templates and their associated assets – Brands, categories, and more – between test and production. Once you’re happy with your test notification, you can copy it to your production environment in just a few clicks.

By default, all of your integrations work in both the test and production environments. But, if you’d prefer an extra layer of security, you can add a test API key for your integration that will only send notifications from Courier’s test environment.

Environments is available to customers on all plans, including our free tier. You can learn more about Environments and how to get started in our Help Center.
New to Courier? Create your free account today and send up to 10,000 notifications every month, for free. Or, chat with us below to learn more.

What we shipped this month: May 2026 Edition
Courier shipped five launches in May 2026: AI Agent in Journeys (GA), the new Journeys API for code-driven flows, Custom Environments, Design Studio styling controls, and Courier Console v3. Each one closes a gap between writing software and shipping the messages that go with it.
By Kyle Seyler
May 20, 2026

Introducing the AI Node in Courier Journeys
The AI node is a new step inside Courier Journeys that classifies users, branches on the result, and writes per-channel copy from a single prompt. Here's what it does, how to set one up, and when it's worth using over a regular condition node.
By Kyle Seyler
May 14, 2026

Using Claude Design, Claude Code, and Courier AI to Create a Multichannel Onboarding Series in 30 Minutes
A walkthrough of building a four-part multichannel onboarding series (email, in-app inbox, mobile push, and Slack) in 30 minutes using Claude Code and Cowork to orchestrate, Claude Design to mock each channel, the courier-template-builder skill to translate mocks into Elemental JSON, the Courier MCP to publish templates, and the Courier CLI to test sends. Covers the strategy behind the sequence and recommendations for anyone doing the same.
By Kyle Seyler
April 17, 2026
© 2026 Courier. All rights reserved.