send_newsletter
Sends a newsletter now, or schedules it, to every contact with a confirmed opt-in inside its audience; unsubscribed contacts never receive it. Needs an approved template. Sending cannot be undone once started.
| Tool name | send_newsletter |
| Permission | newsletters:send |
readOnlyHint | false |
destructiveHint | false |
idempotentHint | true |
openWorldHint | true |
| REST call | POST /v1/newsletters/{newsletter_id}/send |
#What it does
- Sends WhatsApp messages to contacts.
- Safe to repeat with the same idempotency_key.
#Input
The tool takes one flat object. Path, query and body fields of the REST call are merged into it.
| Name | Type | Required | Description |
|---|---|---|---|
newsletter_id | string | yes | ID of the newsletter, from list_newsletters. |
when | string | yes | 'now' or a time in ISO 8601, for example 2026-11-03T10:00:00+01:00. A time without a zone counts as Zurich time. length 3 to 40 |
Arguments added by the MCP server (see Special arguments)
| Name | Type | Required | Description |
|---|---|---|---|
idempotency_key | string | yes | Required. Unique key for this action, for example a UUID. Same key and arguments within 24 hours: first result, nothing done again. up to 255 characters |
#Result
The result has the same content as the REST answer. Lists have at most 50 items per page (default 20); use cursor for the next page.
Errors come back as a tool result with isError: true. The error codes are the ones in Errors.