Book a demo

Schedule Campaign

mailchimp.schedule_campaign
ActionEmailconnection required

Calls the Mailchimp API with the connection's credentials.

Schedule a campaign to send at a future time. Mailchimp only accepts a quarter-hour boundary in UTC — :00, :15, :30 or :45 — and refuses anything else.

Ask about MailchimpAll Mailchimp nodesProvider API docs ↗

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

4 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
campaign_id
The campaign id returned by Mailchimp: Create Campaign or List Campaigns.
stringYes———
schedule_time
When to send, as a UTC ISO 8601 timestamp on a quarter-hour boundary, such as 2026-03-01T14:30:00Z.
stringYes—iso8601 format—
timewarp
Send at that local time in each recipient's own time zone. Mailchimp requires the schedule time to be on the hour for this.
booleanNo———
batch_delivery
Spread the send over batches, as a JSON object — {"batch_delay": 5, "batch_count": 4}.
objectNo——{"batch_count":4,"batch_delay":5}

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "batch_delivery": {
    "batch_count": 4,
    "batch_delay": 5
  }
}

Output

One shape.

result

FieldTypeExample
scheduled
True once Mailchimp accepted the schedule (it answers 204).
boolean—
campaign_id
The campaign that was scheduled.
string—
schedule_time
The time that was sent to Mailchimp.
string—
{
  "campaign_id": "",
  "schedule_time": "",
  "scheduled": false
}

Related Mailchimp nodes

See Schedule 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.

Book a technical demoTalk to sales