Mailchimp node

Add a subscriber to a Mailchimp list (audience) or list subscribers of a list. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

8 min readUpdated September 10, 2026

What this node does

Add a subscriber to a Mailchimp list (audience) or list subscribers of a list.

Use Mailchimp as a clearly defined step in an anymize workflow.

Processes one input.
Provides one output for following steps.
Runs as a regular step in the flow.

Set up the node

01Open a workflow and add Mailchimp from the node catalog.
02Complete the required fields and map values from previous steps.
03Run the node with a small test record and inspect its output.
04Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Choose the required function in Action. The panel then shows the relevant settings.

Add subscriber
List subscribers

Settings

Field	Meaning	Area
Mailchimp API key	Pick the workflow secret that holds your Mailchimp API key (format "<key>-<dc>", e.g. "...-us21"). The key itself is never stored in the workflow.	Protected
Action	Choices: Add subscriber, List subscribers	Standard
List/Audience ID	The ID of your Mailchimp list (audience). Find it in Mailchimp under Audience → Settings → Audience name and defaults.	Standard
Email address	Email address of the subscriber to add.	Standard
Status	Subscription status the new contact should get.	Standard
Extra fields	Optional merge fields like first name (FNAME) or last name (LNAME), depending on your Mailchimp field setup.	Standard
Count	How many subscribers to load (1-1000, default 10).	Standard
Offset	Where in the list to start loading from (for pagination).	Standard
Run once per item	Off (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry.	Standard
If one item fails	"Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file.	Standard
Pause between items (milliseconds)	Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes).	Standard

Inputs and outputs

Input	Meaning	Type
Standard	Receives the complete result from the previous step.	JSON

Output	Meaning	Type
Standard	Makes the result available to the next step as JSON.	JSON

This node can process lists item by item. Error handling and the delay between items are available in advanced settings.

Example and test run

Subscribe a new newsletter contact from a form to Mailchimp: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "list_id": "a1b2c3d4e5",
  "email": "kontakt@beispiel.de",
  "status": "subscribed",
  "merge_fields": {
    "FNAME": "Ada",
    "LNAME": "Lovelace"
  }
}

Access and security

Before activation, review which data enters this step and what its output contains.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

No output: inspect the latest run and confirm that the previous node returned the expected fields.
Empty variable: open the previous step output and use a field name from the real test data.
List processed once: enable per-item execution in advanced settings.