Integrations / Mailchimp
Mailchimp
Mailchimp email marketing platform for managing audiences (lists), campaigns, and list members.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
In Telara
Connect in Telara
OAuth 2.0 authorization-code connection. Mailchimp access tokens do not expire; after exchange, Telara resolves and stores the token's datacenter prefix through the OAuth metadata endpoint.
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
Mailchimp API key. Every key is datacenter-suffixed — a key ending in "-us21" belongs to datacenter "us21", and requests must go to https://us21.api.mailchimp.com/3.0/..., not a fixed host. That suffix is technically embedded in the key string itself, but this catalog's auth engine only does whole-field template substitution into api.base_url (see zendesk.yaml's {subdomain} / auth0.yaml's {domain} pattern) — it has no mechanism to parse or split one stored credential field to derive another. So `server` must be stored as its own credential field (e.g. "us21"), separate from `api_key`: take the substring after the last "-" in the API key value. Find it (or the full base URL) under Mailchimp Account > Extras > API keys.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
- API key
- Server
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| List | Partial — not every record the vendor holds is synced |
| Campaign | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| List | Up to 1 day | Removed records disappear on the next full sync |
| Campaign | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: List, Campaign.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty