Courier integrates with chat and direct message platforms to deliver notifications to users in the apps they already use. Each provider requires specific profile fields to identify the recipient, such as a Slack user ID, Discord channel ID, or phone number.Documentation Index
Fetch the complete documentation index at: https://www.courier.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Available Providers
| Provider | Description |
|---|---|
| Slack | Workspace messaging with Block Kit, threading, webhooks, and slash command support |
| Microsoft Teams | Enterprise messaging via Teams apps and bots with Adaptive Card support |
| Discord | Send direct messages or channel messages via a Discord bot |
| WhatsApp messaging via Twilio with template verification | |
| Facebook Messenger | Messenger delivery using Page-Scoped IDs |
| Viber | Direct messages via a Viber bot account |
| Stream Chat | In-app messaging via the Stream Chat API |
| Chat API | WhatsApp and other chat delivery via the Chat API service |
Provider Overrides
Overrides let you modify parts of a message at send time without changing your notification template. They are passed in themessage payload of a Send request and applied just before Courier hands the message off to the provider.
Provider overrides (message.providers.<key>.override) target a single provider and can pass through fields specific to that provider’s API. Most chat providers support:
bodyoverrides to change the message content, add embeds, blocks, or other provider-specific payload fields.configoverrides to swap credentials or endpoint URLs at send time.