Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Mailchimp" |
| 4 | description: "Public support knowledge for Mailchimp." |
| 5 | category: "authentication" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-06-24T00:00:00Z" |
| 8 | tags: |
| 9 | - "mailchimp" |
| 10 | --- |
| 11 | # Mailchimp |
| 12 | |
| 13 | |
| 14 | ## Mailchimp server prefix is the URL prefix before .admin.mailchimp.com |
| 15 | |
| 16 | When connecting Mailchimp, pass the correct server prefix. It is the part of the Mailchimp URL before `.admin.mailchimp.com`. For example, if the Mailchimp URL is `https://us19.admin.mailchimp.com/`, the server prefix is `us19`. A wrong prefix can cause Mailchimp API calls to fail even if the API key/token itself looks correct. |
| 17 | |
| 18 | ## Use subdomain or dc, not server_prefix, for Mailchimp connectionConfig |
| 19 | |
| 20 | For Mailchimp API connection configuration, send `connectionConfig.subdomain` with the server prefix value, or use the legacy alias `dc`. Do not send `server_prefix`; that key is ignored by the validator and may fall back to a default such as `us21`. The UI label may say Server Prefix, but the API field name is `subdomain`. |
| 21 | |
| 22 | ## Some Mailchimp tools require at least the Mailchimp Essentials plan |
| 23 | |
| 24 | If Mailchimp tools fail despite the connection looking correct, check the customer's Mailchimp plan. Some Mailchimp API/tool capabilities require at least the Mailchimp Essentials plan. A free Mailchimp account may not be enough for the requested tool flow. |
| 25 | |
| 26 | ## Mailchimp Proxy Execute with raw access token also needs subdomain |
| 27 | |
| 28 | When using Proxy Execute with Mailchimp custom connection data, include both the OAuth access token and Mailchimp `subdomain`/server prefix. The endpoint can then be called through `/api/v3/tools/execute/proxy` with `toolkitSlug: "mailchimp"`, `authScheme: "OAUTH2"`, and `val` containing `access_token` plus `subdomain` such as `us20`. |
| 29 | |
| 30 | ## Mailchimp has trigger support in the supported-trigger toolkit list |
| 31 | |
| 32 | Mailchimp appears in the supported-trigger toolkit list. If a customer asks for a specific Mailchimp trigger, verify the exact trigger/event exists in the current toolkit; if it does not, collect the use case and file a toolkit request. |