Why the data center is the first thing to check
| API key example | Data center prefix | Meaning |
|---|
| a1b2c3d4e5f6...-us21 | us21 | Requests route to Mailchimp's us21 server cluster |
| f6e5d4c3b2a1...-us6 | us6 | A DIFFERENT cluster — a list ID from us21 will not resolve here |
Why a mismatch produces "not found" instead of an auth error
A Mailchimp API key's final segment (after the last dash) is the data center identifier, and every API request — including the ones n8n's Mailchimp Trigger makes internally — is implicitly routed using that identifier. If the credential in n8n was created with one API key and later a list ID was copied while logged into a different Mailchimp account or a different data center's instance, the IDs and the routing no longer match, and Mailchimp reports the target as not found rather than as an authentication problem, because from the receiving data center's perspective, that list ID genuinely does not exist there.
This is distinct from the list simply not existing — from the account owner's perspective the audience is right there in the dashboard, which is what makes this error feel wrong at first. It is worth noting Mailchimp's own terminology: "Lists" were renamed to "Audiences" in the product UI some time ago, but the API parameter is still list_id for backward compatibility — so documentation or error messages referencing "list" and the UI referencing "Audience" are describing the same thing, not a separate concept.
Confirm the data center and list ID actually match
- Check the API key's suffix (e.g. -us21) against the Mailchimp account currently logged in when you copied the list/audience ID — they must belong to the same account and data center.
- Re-copy the Audience ID directly from Mailchimp's Audience > Settings > Audience name and defaults page rather than reusing an ID from documentation, an old workflow, or a teammate's note, since list IDs are account-specific.
- If the n8n instance has multiple Mailchimp credentials configured for different accounts, confirm the node is using the credential that matches the account the list ID was copied from.
Fix by rebuilding the credential and re-selecting the list
Regenerate or re-copy the API key directly from the correct Mailchimp account (Account > Extras > API keys), rebuild the n8n credential with that exact key, and then re-select the audience from the node's dropdown rather than pasting a previously known list ID — the dropdown, once the credential is correct, will only show lists that actually match.
If the Trigger still fails after confirming the credential and list match, test with a simpler Mailchimp node action (like listing campaigns) using the same credential to isolate whether the problem is specific to the Trigger's webhook registration step or the credential itself.
Sources checked for this guide
Mailchimp's own developer documentation describes the data-center-sharded API design and the Lists/Audiences terminology; the n8n-specific symptom report is below.
Frequently asked questions
The audience clearly exists in my Mailchimp dashboard — why does n8n say it's not found?
Mailchimp's API is data-center-sharded. If the API key used in the n8n credential belongs to a different data center or account than where the list ID was copied from, the request is misrouted and reports not-found rather than an auth error.
Do I need to create a new API key to fix this?
Only if the current one is confirmed to belong to the wrong account or data center. If it matches, the fix is usually re-selecting the audience from n8n's dropdown instead of a pasted ID.
How do I know which data center my API key belongs to?
The suffix after the final dash in the key itself (for example -us21) is the data center identifier — it must correspond to the same account where the audience/list ID was copied from.
Are "List" and "Audience" different things in Mailchimp?
No — Mailchimp renamed "Lists" to "Audiences" in its UI, but the API parameter is still called list_id for backward compatibility. Error messages and older documentation referencing "list" mean the same object as the "Audience" you see in the dashboard.
