Courier
Notification infrastructure with visual journeys.
Courier blends notification infrastructure with marketing-style journeys. Visual template builder, drop-in inbox UI, native Slack and Teams routing. Bridges product notifications and customer engagement.
An agent stack treats email as a two-way primitive. Inbound has to arrive as structured JSON a tool call can consume, sends have to be safe to retry when a model loop repeats itself, and every action needs an audit trail. A provider without inbound parsing only solves half the problem.
Against inbound parsing into tool calls and model-generated sends that must not duplicate, Courier covers webhook coverage, event stream, batch sending, SDK breadth, and multi-tenant support, and does not cover inbound parsing, idempotency keys, and operating track record. Whether that gap matters depends on how central those are to the build.
- Inbound parsing: No
- Idempotency keys: No
- Webhooks: Yes
- Operating since: 2019
- Event stream: Yes
- Best published rate per 1,000: Tiers not published in comparable form
- Batch sending: Yes
- SDKs: node, python, go, ruby, php, java
- Multi-tenant: Yes
Inherits providers you connect.
Teams that need both product notifications and marketing-style journeys.
- › Visual journey editor
- › Native Slack/Teams routing
- › Drop-in inbox component
- › Less code-first than Knock
- › Pricing climbs with volume
Features at a glance
| API | Yes |
| SMTP | No |
| SDKs | node, python, go, ruby, php, java |
| Webhooks | Yes |
| Templates | rich |
| React Email | No |
| Batch send | Yes |
| Scheduled send | Yes |
| Suppressions | Yes |
| Multi-tenant | Yes |
| Inbound parsing | No |
| Event stream | Yes |
| Idempotency keys | No |
| Dedicated IP | No |