Send Campaign
mailchimp.send_campaign
ActionEmailconnection required
Calls the Mailchimp API with the connection's credentials.
Send a campaign now. Mailchimp accepts the request and sends asynchronously, so success here means 'queued', not 'delivered' — poll Get Campaign for status. This cannot be undone.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Mailchimp
- Secret shape
- the Mailchimp API key (…-<dc>)
- Config it needs
- dc
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
campaign_id The campaign id returned by Mailchimp: Create Campaign or List Campaigns. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
sent True once Mailchimp queued the send (it answers 204). | boolean | — |
campaign_id The campaign that was queued. | string | — |
{
"campaign_id": "",
"sent": false
}See Send Campaign run in a workflow.
In a technical demo we add the Mailchimp connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.