Does n8n have a Mailchimp trigger?

Yes. The Mailchimp Trigger is webhook-based and bound to one audience (list). It fires on Subscribe, Unsubscribe, Profile Updated, Email Address Updated, Cleaned and Campaign Sent, filtered by source: user, admin or API.

Do Mailchimp steps convert automatically?

No. Mailchimp actions are not in the converter's mapped list, so each step arrives as a marked placeholder with its props (list ID, email, merge fields, tags). The report also lists the Mailchimp credential to create.

API key or OAuth2 in n8n?

Mailchimp's own rule, quoted in the n8n docs: an API key for your own account, OAuth2 when you connect other people's accounts.

Is there an upsert for subscribers?

Pipedream has Add or Update Subscriber. n8n's Member → Update sends a PUT without status_if_new, so it only works for existing members. For a real upsert send PUT /lists/{id}/members/{email} with status_if_new through HTTP Request and the Mailchimp credential.

Pipedream Mailchimp steps in n8n

Updated 2026-10-21 · 3 min read · n8n: Mailchimp (Native n8n node)

Mailchimp workflows in Pipedream are usually list hygiene: a form, a Stripe payment or a CRM change adds a subscriber, sets tags, and sometimes a new subscriber fires a welcome flow somewhere else. n8n has a native Mailchimp node and a Mailchimp Trigger, so nearly every step has a direct home.

The n8n side

Mailchimp node (n8n-nodes-base.mailchimp):

Resource	Operations
Campaign	Delete, Get, Get All, Replicate, Resend (to non-openers), Send
List Group	Get All
Member	Create, Delete, Get, Get All, Update
Member Tag	Add tags, Remove tags (Create / Delete in the UI)

Mailchimp Trigger: a webhook registered on one audience. Events: Subscribe, Unsubscribe, Profile Updated, Email Address Updated, Cleaned, Campaign Sent. A Sources filter decides whether changes made by the subscriber, an admin or the API fire it.

What maps where

Pipedream (app `mailchimp`)	In n8n	Status
Add or Update Subscriber	HTTP Request PUT with `status_if_new` (upsert), or Member → Create / Update	manual
Add Or Remove Members Tags	Member Tag → Add / Remove	manual
Unsubscribe Email	Member → Update, status `unsubscribed`	manual
Search Members/Subscribers	Member → Get / Get All	manual
Create Campaign, Send a Campaign	Campaign → Send; creation via HTTP Request	manual
Get A Campaign Report, Add Note to Subscriber	HTTP Request with the Mailchimp credential	manual
New Subscriber (Instant), New Unsubscriber (Instant), New or Updated Subscriber (Instant)	Mailchimp Trigger (Subscribe / Unsubscribe / Profile Updated)	manual
New Campaign (polling)	Schedule Trigger + Campaign → Get All	manual

The converter does not map Mailchimp actions yet. Each step becomes a placeholder node that keeps the original props (list ID, email, merge fields, tags) in a comment, and the trigger becomes a Manual Trigger with a note naming the Pipedream source. Rebuilding is mostly copying those values into the Mailchimp node.

Mailchimp credentials in n8n

API key: Account → Extras → API keys. The key ends with the data center suffix (-us21), which n8n uses to build the URL.
OAuth2: register an app in Mailchimp; use it when the workflow serves several client accounts.

Pipedream never exports tokens, so either way you connect Mailchimp again in n8n.

Typical migration: paid customers to an audience

Pipedream: Stripe New Payment → Mailchimp Add or Update Subscriber → Add Or Remove Members Tags (customer). n8n: Stripe Trigger → Mailchimp → Member → Create (status subscribed, merge fields from the Stripe customer) → Member Tag → Add. For returning customers, add an error branch on Create ("Member Exists") that routes to Member → Update, or use one HTTP Request PUT with status_if_new.

Mailchimp migration pitfalls

Connection limit. Mailchimp allows 10 simultaneous connections per user, not per key, and answers 429 TooManyRequests. A Split in Batches loop with parallel requests hits it quickly; keep batch size small or use the batch endpoint.
Trigger per audience. One Mailchimp Trigger watches one list. A Pipedream source that watched several lists becomes several triggers or one webhook with an audience filter.
Email as ID. Mailchimp member IDs are the MD5 hash of the lowercase email, but the member endpoints also accept the plain email, which is what the n8n node sends.
Double opt-in. Status pending sends a confirmation email; subscribed skips it. Keep the same value the Pipedream step used.

How to move your Mailchimp workflows

Export the workflows from Pipedream.
Upload them on /convert; the free report lists each Mailchimp step with its props and the credential to create.
Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

More in the Pipedream to n8n guide. Related: SendGrid, Typeform, HubSpot.

FAQ

Does n8n have a Mailchimp trigger?: Yes. The Mailchimp Trigger is webhook-based and bound to one audience (list). It fires on Subscribe, Unsubscribe, Profile Updated, Email Address Updated, Cleaned and Campaign Sent, filtered by source: user, admin or API.
Do Mailchimp steps convert automatically?: No. Mailchimp actions are not in the converter's mapped list, so each step arrives as a marked placeholder with its props (list ID, email, merge fields, tags). The report also lists the Mailchimp credential to create.
API key or OAuth2 in n8n?: Mailchimp's own rule, quoted in the n8n docs: an API key for your own account, OAuth2 when you connect other people's accounts.
Is there an upsert for subscribers?: Pipedream has Add or Update Subscriber. n8n's Member → Update sends a PUT without status_if_new, so it only works for existing members. For a real upsert send PUT /lists/{id}/members/{email} with status_if_new through HTTP Request and the Mailchimp credential.