Mailchimp
Mailchimp support centers on audience-backed contact management and campaign reads. Vorlek normalizes the subscriber hash, merge fields, and cursor pagination.
Connection setup
- Create a Mailchimp Marketing API key. The key includes a data-center suffix such as
-us7. - Pick the audience/list Vorlek should write to. If the account has exactly one audience, Vorlek can auto-detect it.
- Connect with
vorlek connect mailchimp --api-key xxxxx-us7 --list-id a1b2c3d4e5. - Run
get_connection_status; the response includes the audience id and name when available.
Gotchas
- An audience/list id is required for predictable writes. Multiple audiences without a configured list return a connection error.
- Contact ids are Mailchimp subscriber hashes:
md5(lowercase(trim(email))). - Transactional email is Mandrill, a separate Mailchimp product. Vorlek returns
TOOL_NOT_SUPPORTEDforsend_transactional. - Mailchimp offset pagination is wrapped in an opaque Vorlek cursor; do not parse it.
Tool coverage
| Tool | Support | Notes |
|---|---|---|
upsert_contact | Yes | Writes to the configured audience and maps custom properties to merge fields. |
get_contact | Yes | Reads one audience member by email hash for read-after-write verification. |
send_transactional | No | Returns TOOL_NOT_SUPPORTED; Mandrill is not part of the launch surface. |
get_campaign_stats | Yes | Normalizes campaign metrics where Mailchimp exposes them. |
list_templates | Yes | Returns saved template ids and names. |
list_campaigns | Yes | Normalizes Mailchimp status values into the Vorlek status set. |