Short answer: Drop the "Mailchimp → List Members" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
List ID list_id | string | Required | Mailchimp audience (list) ID — a 10-char hex string. Find in Audience > Settings > Audience name & defaults. |
Count count | string | Optional | Count. e.g. "10" |
Offset offset | string | Optional | Offset. e.g. "0" |
Status Filter status | options | Optional | Status Filter. Options: All, Subscribed, Unsubscribed, Pending |
{"list_id": "e.g. a1b2c3d4e5","count": "10","offset": "0","status": "{{trigger.status}}"}
{"members": [{"id": "abc","status": "subscribed","email_address": "user@example.com"}],"total_items": 1}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.