Mailchimp Connector

Tajo’s Mailchimp connector is in progress. The code exists, but it has not yet passed a run against a live Mailchimp account.

What the code does

• Reads audiences and their members with status, merge fields and tags, plus segments, interest groups, signup forms and surveys.
• Reads e-commerce stores, customers, orders, carts, products and promo codes.
• Reads campaigns with their content and reports, templates, landing pages, classic automations and SMS campaigns.
• Adds or updates one audience member, adds or removes a member’s tags, and registers an audience webhook for changes such as subscribes, unsubscribes and profile updates.
• Treats a member’s status as marketing consent: an unsubscribed or cleaned member is a suppression.

Not available today

• Migration of automations, templates or campaigns into Brevo
• Engagement metrics written to contact attributes
• Real-time sync. The audience webhook exists in code and has not been verified.

Open-Source Implementation Map

This section is derived from official or public repository material discovered for the Mailchimp connector. Use it as the engineering companion to the setup guide above: it shows where the API surface lives, what implementation assets exist, and how Tajo should translate them into reliable Brevo sync behavior.

Repository Snapshot

Integration Shape

graph LR
  Source["Mailchimp API / repository"] --> Auth["Auth and scopes"]
  Source --> Objects["Objects, events, and schemas"]
  Auth --> Tajo["Tajo connector runtime"]
  Objects --> Tajo
  Tajo --> Brevo["Brevo contacts, attributes, lists, campaigns"]
  Tajo --> Ops["Backfill, cursor, retries, logs"]

What To Reuse

• mailchimp-client-lib-codegen
• This tool is used to auto-generate and publish both Mailchimp Marketing and Transactional client libraries.
• Quick start
• Generate clients
• Published clients — Internal

Tajo Revamp Checklist

• Keep authentication setup aligned with the vendor docs and the public repository’s current API shape.
• Map primary resources into explicit Tajo sync objects with stable external IDs.
• Prefer cursor-based or updated-at incremental sync where the API exposes it; otherwise document the fallback.
• Treat webhook handlers as idempotent and replay-safe, especially for order, contact, ticket, and campaign events.
• Capture pagination, rate limits, retry headers, and partial-failure behavior in connector smoke tests.
• Keep examples small and runnable against sandbox or test-mode accounts.

Sources

• mailchimp/mailchimp-client-lib-codegen
• Vendor documentation