List Campaigns

mailchimp.list_campaigns
ActionEmailconnection required

Calls the Mailchimp API with the connection's credentials.

Fetch a page of the account's campaigns, optionally limited to one status, type, audience or send window.

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

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

FieldTypeRequiredDefaultConstraintsExample
status
Return only campaigns in this state.
stringNo—one of "save", "paused", "schedule", "sending", "sent"—
campaign_type
Return only campaigns of this kind.
stringNo—one of "regular", "plaintext", "absplit", "rss", "variate"—
list_id
Return only campaigns sent to this audience.
stringNo———
since_send_time
Return only campaigns sent at or after this time, ISO 8601.
stringNo—iso8601 format—
sort_dir
Order the page by send time, ascending or descending.
stringNo—one of "ASC", "DESC"—
count
How many records to return on this page; Mailchimp caps a page at 1000.
numberNo101–1000—
offset
How many records to skip before this page, for paging through a collection.
numberNo0≥ 0—

Example configuration

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

{
  "count": 10,
  "offset": 0
}

Output

One shape.

result

FieldTypeExample
items
The records on this page, exactly as Mailchimp returned them.
array—
count
How many records this page carried.
number—
total
Total records matching the query, from the response's total_items; falls back to the page's own row count when Mailchimp reports no total.
number—
{
  "count": 0,
  "items": [],
  "total": 0
}

See List Campaigns 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.