by Customer.io
Trigger a broadcast
Sends an API-triggered broadcast now or at a scheduled time, to its saved audience or to the people, emails or filter you pass, with data for its Liquid placeholders.
Description
Set the broadcast up in Customer.io first. It reaches only people already in the workspace: unknown recipients fail the request unless you set `email_ignore_missing` or `id_ignore_missing` to `true`. Reference `data` in the message as `{{trigger.<key>}}`. This endpoint allows one request every 10 seconds.
trigger-broadcast.md
Trigger a broadcast
Sends an API-triggered broadcast now or at a scheduled time, to its saved audience or to the people, emails or filter you pass, with data for its Liquid placeholders.
Set the broadcast up in Customer.io first. It reaches only people already in
the workspace: unknown recipients fail the request unless you set
email_ignore_missing or id_ignore_missing to true. Reference data in
the message as {{trigger.<key>}}. This endpoint allows one request every 10
seconds.
Set up
Use the first option your agent supports.
API (official)
- Base URL: https://api.customer.io
- Endpoint:
POST /v1/campaigns/{broadcast_id}/triggers - Auth: send the header
Authorization: Bearer $CUSTOMERIO_API_KEY - Get a key: https://fly.customer.io/settings/api_credentials?keyType=app
- Docs: https://docs.customer.io/integrations/api/app/
Before doing anything else, make one read-only call to confirm access.
Rules
- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.
Built from these files in the repository
The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.
Ways in
| Route | Source | Call | Required | Docs |
|---|---|---|---|---|
| Official | POST /v1/campaigns/{broadcast_id}/triggers | API key in $CUSTOMERIO_API_KEY | Docs |