Reference · built on requestConnectorMarketing, reviews & analytics

Mailchimp

Audiences, members, campaigns, reports, and e-commerce data from a Mailchimp account, with signed list webhooks.

Request accessPricing ↗

About

Mailchimp is an email marketing platform from Intuit. An account holds audiences and their members, merge fields, tags, segments, campaigns, classic automations and customer journeys, campaign reports, and e-commerce data synced from a store. The Marketing API is version 3.0, served from the account's data center under https://<dc>.api.mailchimp.com/3.0/.

Through Fibric, an operator reads members and campaign reports, joins them with orders and support conversations, and proposes a member update, a tag, or a campaign action for your approval. Approved writes happen once and leave a record of what changed and why.

This is a reference listing. It documents what Fibric would read from Mailchimp and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Audiences and their members through List members info, with status of subscribed, unsubscribed, cleaned, pending, or transactional
  • Merge fields, tags, segments, and interest categories on each audience
  • Campaign reports through GET /reports/{campaign_id}, with email activity, click details, open details, unsubscribes, and abuse reports
  • List webhooks for subscribe and unsubscribe events, posted as form-encoded data and signed with X-Mailchimp-Signature
  • E-commerce stores, customers, orders, carts, and promo codes synced to the account
  • Batch operation results through POST /batches and batch webhooks

Proposed actions

  • Target capability: propose a member add or update through PUT /lists/{list_id}/members/{subscriber_hash}
  • Target capability: propose a tag or merge field change on a member through PATCH /lists/{list_id}/members/{subscriber_hash}
  • Target capability: propose archiving a member through DELETE /lists/{list_id}/members/{subscriber_hash}
  • Target capability: propose a campaign schedule, send, unschedule, or cancel-send through the /campaigns/{campaign_id}/actions endpoints

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Unschedule a send that promises what you cannot ship

    The operator checks a scheduled campaign against stock and cutoff dates from your store. If the offer cannot be honored, it proposes the unschedule action for your approval.

    With Backorder Notice, Holiday Cutoff

  • Spot a cohort that stopped opening

    Campaign reports show who opened and clicked. The operator joins that with order history and proposes a tag on members who went quiet, so your automation can act.

    With Churn Watch, Cohort Watch

  • Keep unsubscribes in the help desk record

    When a webhook fires for unsubscribe, the operator matches the email to the customer in your support tool and proposes a note explaining the change.

    With Contact Drivers

  • Reach affected customers during an outage

    The operator drafts the segment of affected members and proposes a campaign send. Nothing goes out until you approve.

    With Outage Notice

Requirements

  • A Mailchimp account and its data center prefix, which forms the base URL https://<dc>.api.mailchimp.com/3.0/
  • An API key, or an OAuth 2 app authorized by a user whose role covers the audiences and campaigns involved
  • For change notifications, a webhook on each audience created through POST /lists/{list_id}/webhooks, and the signing_secret it returns once
Authentication
An API key sent as the password in HTTP basic authentication with any username, or an OAuth 2 bearer token; access follows the role of the user who created it.

Limits

  • The Marketing API allows 10 simultaneous connections per account; a request past that returns 429
  • API calls time out after 120 seconds
  • Webhook payloads arrive as application/x-www-form-urlencoded, not JSON
  • Batch results are a gzipped tar archive; the download URL expires after 10 minutes and results are kept for seven days

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Mailchimp ↗

Questions and answers

How is a member identified in the API?
By subscriber_hash, the lowercase MD5 hash of the member's email address. It is the id in the path for get, add or update, update, and archive calls on /lists/{list_id}/members.
How are webhook requests authenticated?
Mailchimp signs each request with HMAC-SHA256 over the timestamp and raw body, keyed by the signing_secret returned once when the webhook is created through POST /lists/{list_id}/webhooks. The signature arrives in the X-Mailchimp-Signature header and should be compared with a timing-safe function.
What are the rate limits?
The Marketing API limits an account to 10 simultaneous connections and returns 429 when that is exceeded. Calls time out after 120 seconds. Large jobs go through POST /batches, which returns results as a gzipped tar archive kept for seven days.
Ask about Mailchimp

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Mailchimp through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy