Skip to main content

Prerequisites

  • An HTTPS endpoint you control, ready to receive Courier’s webhook
  • The authentication your endpoint expects, if any

Setup

Open the . Enter your webhook HTTP address and choose an authentication model.
Custom Provider
You can now add the Custom Provider to any Push channel. Add a Push channel, then open the Channel Settings modal.
Custom Provider Settings
“Custom” appears in the list of installed providers.
Installed Custom Provider
Add a title and blocks in the designer. Courier sends them to your webhook as plain text and as an array of blocks.
Custom Provider Designer
When the message sends, your webhook receives a payload like this:

Profile requirements

No profile data is required. Courier posts the rendered message to your endpoint, and your endpoint decides how to address the recipient.

Overrides

covers the two levels and which one wins. An override changes what Courier sends to your custom provider. You can override the body, headers, method, and url fields. body is deep-merged into the request, so fields you leave out are still sent.

Provider details

Courier recommends routing to the channel. Naming this key in routing.channels instead is supported, and sends through just this provider.

Send to a specific provider

When that is worth doing, and what you give up: failover, channel priority, and providers you add later.