Menu

Mattering Automations Mailchimp integration

Connect Mailchimp to Mattering Automations: audiences, members by plain email, tags, segments, campaign drafts, and reports as workflow steps, authenticated with your Mailchimp API key and routed to the right data center automatically.

The Mattering Automations Mailchimp integration adds Mailchimp to your automation canvas: manage audiences and their members by plain email address, tag and segment contacts, assemble campaign drafts and set their content, send test previews, and read campaign reports down to per-recipient opens and per-link clicks.

Setup takes a few minutes: create an API key in Mailchimp, attach it as a credential in Mattering, and test the connection. There is no server or data center field to fill in, because a Mailchimp API key ends with the name of its data center and the integration derives the server from the key itself. This guide walks through each step and ends with the full node reference.

The send model is draft-first by construction. Mailchimp: Create Campaign (Draft) emails nobody: a campaign sits in save status through content and settings changes, and only two flagged nodes, Mailchimp: Send Campaign (Sends Real Email) and Mailchimp: Schedule Campaign (Sends Real Email at the Scheduled Time), commit a real send. Keep both behind a condition, an approval step, or a manual run, preview with Mailchimp: Send Test Email, and verify the integration with read nodes only.

Before you start

  • A Mailchimp account with at least one audience. API keys are available on every Mailchimp plan, including the free tier.
  • Access to the Mailchimp account settings to create an API key (Account, then Extras, then API keys).
  • A Mattering workspace with access to the Automations app.
  • For the report nodes: at least one sent campaign, since Mailchimp only returns reports for campaigns that have actually gone out.

Create a Mailchimp API key

Mattering authenticates to Mailchimp with an account API key, sent on every request using the HTTP Basic scheme Mailchimp documents. The key does double duty: the characters after its last hyphen name your account's data center, and the integration reads the server address from that suffix, so the key is the only credential value you store.

Log in to Mailchimp and open Account > Extras > API keys.
Create a new API key.
Copy the key exactly as issued, including everything after the last hyphen.
The suffix after the key's last hyphen (for example us21) is your data center, and the integration derives the server address from it. A key stored without its suffix cannot be routed to any server, so always store the full value exactly as Mailchimp issued it.

Connect Mailchimp to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Mailchimp from the list.
Click Create new credential, paste your API key, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection: Mattering derives the data center from your key's suffix and runs Mailchimp's documented ping health check against it, confirming the key and the routing in one call without returning any account data.
Click Connect. All 39 Mailchimp nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: a Mailchimp section should list the query and action nodes. Drop Mailchimp: Ping (Health Check) onto the canvas and run a test step. It takes no parameters and returns a health status without any account data; a 401 here means the key is wrong. Then run Mailchimp: List Audiences: the audience ids it returns feed nearly every other node, so note the id of the audience your automations will work in.

To confirm the member surface, run Mailchimp: Get Member with your own email address (a 404 simply means the address is not in that audience), or Mailchimp: List Campaigns for the campaign surface. Everything in the verify path is read-only; nothing here can reach Mailchimp: Send Campaign (Sends Real Email) or Mailchimp: Schedule Campaign (Sends Real Email at the Scheduled Time), the only two nodes that deliver email to an audience.

Node reference

39 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 22

Mailchimp: Get Audience

mailchimp_get_audience

Get one audience's full settings and stats: contact info, campaign defaults, permission reminder, double opt-in flag, and member counts (data.stats.member_count and friends).

Mailchimp: Get Campaign

mailchimp_get_campaign

Get one campaign's full details: status, recipients, settings (subject line, from name, reply-to), tracking options, and send_time. data.status tells an automation whether the campaign is still a draft (save) or already sent.

Mailchimp: Get Campaign Click Details

mailchimp_get_click_details

Per-URL click report for a sent campaign: every tracked link with its total and unique clicks and click percentages. Answers which link in the email actually performed.

Mailchimp: Get Campaign Content

mailchimp_get_campaign_content

Get the HTML and plain-text content of a campaign (data.html and data.plain_text). Useful for auditing a draft before send or feeding campaign copy into another step.

Mailchimp: Get Campaign Email Activity

mailchimp_get_email_activity

Per-recipient activity for a sent campaign: each member's opens, clicks, and bounces with timestamps. The raw feed for engagement scoring or a clicked-but-did-not-convert follow-up automation. Large campaigns return many rows; page with count and offset.

Mailchimp: Get Campaign Report

mailchimp_get_campaign_report

Get the full report for one sent campaign: opens, clicks, bounces, unsubscribes, abuse complaints, and timing. The key numbers live at data.opens.open_rate and data.clicks.click_rate.

Mailchimp: Get Member

mailchimp_get_member

Look up one contact in an audience by email address and return their full profile: status, merge fields, tags, and engagement stats. A contact not in the audience returns a 404, which makes this the standard exists-check before an add or update step.

Mailchimp: Get Segment

mailchimp_get_segment

Get one segment's details: name, type, member_count, and for saved segments the matching conditions.

Mailchimp: Get Template

mailchimp_get_template

Get one template's details (name, type, category, creation info).

Mailchimp: Get Template Default Content

mailchimp_get_template_default_content

Get a template's editable sections and their default content (data.sections). The section names are the keys to fill in Set Campaign Content's template reference.

Mailchimp: List Audiences

mailchimp_list_audiences

List the audiences (lists) in the Mailchimp account, with their ids, settings, and stats (member_count, open_rate, click_rate). Audience ids from data.lists[].id feed every other Mailchimp node.

Mailchimp: List Campaign Reports

mailchimp_list_campaign_reports

List summary reports for sent campaigns: emails_sent, opens, clicks, bounces, and unsubscribes per campaign. The feed for a recurring performance digest automation.

Mailchimp: List Campaigns

mailchimp_list_campaigns

List campaigns in the account with filters for status, type, audience, and send window. Campaign ids from data.campaigns[].id feed the get/update/send/content/report nodes.

Mailchimp: List Member Tags

mailchimp_list_member_tags

List the tags currently on one contact, looked up by email address. Returns data.tags[] with id, name, and date_added.

Mailchimp: List Members

mailchimp_list_members

List the contacts in an audience, optionally filtered by subscription status. Each member carries email, status, merge fields, tags, and engagement stats. Member outputs contain personal data (names, emails) that persists in execution records.

Mailchimp: List Merge Fields

mailchimp_list_merge_fields

List an audience's merge fields (custom contact attributes): tag, name, type, and required flag. The tags returned here (FNAME, LNAME, ...) are the keys to use in the member nodes' merge_fields objects.

Mailchimp: List Segment Members

mailchimp_list_segment_members

List the contacts currently in a segment (works for saved and static segments, including tag membership via the tag's segment id). Member outputs contain personal data that persists in execution records.

Mailchimp: List Segments

mailchimp_list_segments

List an audience's segments with their ids, type (saved, static, or fuzzy), and member counts. Tags appear here as static segments, so this also enumerates tag membership counts.

Mailchimp: List Templates

mailchimp_list_templates

List the account's email templates with ids, names, and types. Template ids from data.templates[].id plug into Set Campaign Content's template reference.

Mailchimp: Ping (Health Check)

mailchimp_ping

Mailchimp's documented API health check: confirms the API key and its data center are wired correctly without returning any account data. Returns data.health_status on success; a bad key returns a 401. Use this as the first node when debugging a Mailchimp connection.

Mailchimp: Search Members

mailchimp_search_members

Search for contacts across the whole account (or one audience) by name, email, or other profile text. Returns exact_matches and full_search result groups, each holding member objects. Handy when an automation has an email but not the audience id.

Mailchimp: Search Tags

mailchimp_search_tags

Search an audience's tags by name, or list every tag on the audience when the name is left blank. Returns data.tags[] with id and name.

Action nodes 17

Mailchimp: Add Member

mailchimp_add_member

Add a NEW contact to an audience. Fails with a 400 if the email already exists in the audience; use Mailchimp: Add or Update Member (upsert) when the contact may already be there. Status 'pending' sends a confirmation email (double opt-in); 'subscribed' adds them directly and requires that you already have their consent.

Mailchimp: Add or Remove Member Tags

mailchimp_update_member_tags

Add and/or remove tags on one contact in a single call, looked up by email address. Each tag entry sets status active (add) or inactive (remove); a tag that does not exist yet is created when added. Fully reversible by flipping the statuses back. Returns 204 with an empty body.

Mailchimp: Add or Update Member (Upsert)

mailchimp_upsert_member

Add a contact if the email is new to the audience, or update them if it already exists (Mailchimp's PUT upsert). The idempotent workhorse for sync automations: safe to run repeatedly for the same address. The email field drives both the lookup hash and the stored email_address.

Mailchimp: Add/Remove Segment Members (Batch)

mailchimp_update_segment_members

Batch add and/or remove audience members in a STATIC segment by email address. The response reports members_added, members_removed, and per-email errors (e.g. addresses that are not in the audience). Reversible: run again with the lists swapped.

Mailchimp: Archive Member

mailchimp_archive_member

Archive a contact by email address (Mailchimp's DELETE on a member). This is the RECOVERABLE removal: the contact's history is kept, they stop counting toward the audience, and re-adding the same email (e.g. via the upsert node) restores them. Mailchimp's permanent PII delete is deliberately not offered as a node. Returns 204 with an empty body.

Mailchimp: Cancel Campaign Send (Pro Only)

mailchimp_cancel_campaign_send

Emergency stop: cancel a campaign that is CURRENTLY SENDING. Documented as included with Mailchimp Pro only; other plans get an error. The stop is permanent: a canceled campaign cannot resume, so recipients already processed keep the email and the rest never get it. Returns 204 with an empty body.

Mailchimp: Create Audience

mailchimp_create_audience

Create a new audience (list). Mailchimp requires the sender contact block and campaign defaults up front because they appear in the footer of every email sent to the audience. Note that most plans cap the number of audiences; reusing one audience with tags is Mailchimp's own recommendation.

Mailchimp: Create Campaign (Draft)

mailchimp_create_campaign

Create a campaign DRAFT. Nothing is emailed by this node: the campaign sits in save status until content is set and a separate send or schedule node fires it. The returned data.id feeds Set Campaign Content and the send/schedule nodes.

Mailchimp: Create Static Segment

mailchimp_create_static_segment

Create a STATIC segment (fixed membership you control, the same mechanism behind tags) in an audience, optionally seeding it with member emails. Emails that are not already audience members are skipped by Mailchimp and reported in the response. This node always sends static_segment, so it creates static segments only; rule-based saved segments are built in the Mailchimp UI.

Mailchimp: Schedule Campaign (Sends Real Email at the Scheduled Time)

mailchimp_schedule_campaign

Schedule the campaign to SEND REAL EMAIL to its full audience at the given UTC time. Flagged destructive because it commits an actual send; the undo is Mailchimp: Unschedule Campaign, which works only until the send time arrives. Mailchimp requires the time to fall on a quarter hour (:00, :15, :30, :45). Returns 204 with an empty body.

Mailchimp: Send Campaign (Sends Real Email)

mailchimp_send_campaign

SENDS THE CAMPAIGN NOW to its entire selected audience or segment. This delivers real email to real recipients immediately and cannot be undone once sending completes (cancel-send exists only on Mailchimp Pro, and only while the send is in flight). Verify the draft with Get Campaign and Send Test Email first. The campaign must have content and complete settings or Mailchimp returns a 400. Returns 204 with an empty body on success.

Mailchimp: Send Test Email

mailchimp_send_test_email

Send a TEST version of the campaign to the listed addresses only. This is the safe way to preview a campaign from an automation before the real send, but it does deliver actual email to those test inboxes, so point it at your own addresses. Returns 204 with an empty body.

Mailchimp: Set Campaign Content

mailchimp_set_campaign_content

Set a draft campaign's content: raw HTML (Mailchimp auto-generates the plain-text version unless you provide one), or a template reference via extra_body, e.g. {"template": {"id": 2000123, "sections": {"body": "<p>Hello</p>"}}}. Run this between Create Campaign and Send/Schedule.

Mailchimp: Unschedule Campaign

mailchimp_unschedule_campaign

Cancel a SCHEDULED campaign that has not started sending yet, returning it to draft. This is the safety valve for the schedule node; it cannot stop a campaign that is already sending. Returns 204 with an empty body.

Mailchimp: Update Audience

mailchimp_update_audience

Update an audience's settings. Only the fields you fill are changed; everything else keeps its current value. Use extra_body for other documented settings such as contact or double_optin.

Mailchimp: Update Campaign Settings

mailchimp_update_campaign

Update a draft campaign's settings (subject line, from name, reply-to, title) and/or its recipients. Only the objects you fill are sent; within settings, include every field you want to keep, as Mailchimp replaces the provided object's values.

Mailchimp: Update Member

mailchimp_update_member

Update an EXISTING contact's profile or status by email address. Only the fields you fill are changed. Fails with a 404 if the email is not in the audience; use the upsert node when it might not be. Setting status to unsubscribed is how an automation opts a contact out.

Using the integration

On the automation canvas

Mailchimp nodes chain with every other node: a form lead can flow through Mailchimp: Add or Update Member (Upsert) and Mailchimp: Add or Remove Member Tags the moment it arrives, and a scheduled Mailchimp: List Campaign Reports sweep can land open and click rates as tasks in Mattering Productivity or records in a Mattering database, next to the rest of the team's work.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can look up contacts, read campaign drafts, and pull report numbers through the same nodes your workflows use. The member lookups, campaign reads, and report nodes are read-only, which makes them the safest Mailchimp surface to hand an agent.

The draft-first campaign model

Mailchimp: Create Campaign (Draft) creates a campaign that emails nobody, Mailchimp: Set Campaign Content fills in raw HTML or a template's editable sections, and Mailchimp: Send Test Email previews it to only the addresses you list. Mailchimp: Send Campaign (Sends Real Email) then delivers to the entire selected audience immediately, and Mailchimp: Schedule Campaign (Sends Real Email at the Scheduled Time) commits the same send on a timer; Mailchimp: Unschedule Campaign is its undo, working only until the send time arrives. Mailchimp: Cancel Campaign Send (Pro Only) is an emergency stop for a send already in flight, documented as included with Mailchimp Pro only.

Members by plain email, no hashes

Mailchimp's API addresses a contact by the MD5 hash of their lowercased email, but you never compute it: every member node takes a plain email field and hashes it for you. The lifecycle is deliberate: Mailchimp: Add Member is a strict create that fails on an existing address, Mailchimp: Add or Update Member (Upsert) is the idempotent sync workhorse, Mailchimp: Update Member changes an existing contact only, and Mailchimp: Archive Member is the recoverable removal, restored by re-adding the same email. Mailchimp's permanent PII delete is deliberately not shipped: it destroys the contact's history and permanently blocks re-importing the address, so it stays a console decision.

Tags and static segments

Tags are managed per member: Mailchimp: Add or Remove Member Tags adds and removes them in one call, creating unknown tags on add, and Mailchimp: List Member Tags and Mailchimp: Search Tags read them back. Segments created here are static: Mailchimp: Create Static Segment builds a fixed-membership segment and Mailchimp: Add/Remove Segment Members (Batch) changes its membership in batches with per-email error reporting. Rule-based saved segments are built in the Mailchimp UI and read through Mailchimp: List Segments and Mailchimp: Get Segment.

Reports and polling

Mailchimp: Get Campaign Report returns a sent campaign's opens, clicks, bounces, and unsubscribes, Mailchimp: Get Campaign Email Activity lists per-recipient activity with timestamps, and Mailchimp: Get Campaign Click Details shows which links performed. There is no inbound Mailchimp trigger in this integration, so react to change by polling: run the report or list nodes on a schedule and act on what moved. Reports only exist for campaigns that have been sent.

Troubleshooting

Test Connection fails saying it cannot find the data center suffix
The stored key is missing the part after its last hyphen, which names your data center. Store the credential again with the key exactly as Mailchimp issued it, suffix included. The integration reads the server address from that suffix; without it there is nowhere to send the request.
Test Connection fails with a 401
The key is invalid, was revoked in Mailchimp, or picked up stray whitespace when pasted. Create a fresh key under Account > Extras > API keys and update the credential on the connector. Mailchimp: Ping (Health Check) is the fastest recheck after the fix, since it exercises the key and the routing with no other moving parts.
Adding a contact returns a 400 saying the member already exists
Mailchimp: Add Member is a strict create and refuses an email that is already in the audience. Switch to Mailchimp: Add or Update Member (Upsert), which adds the contact if new and updates them if not, and is safe to run repeatedly for the same address.
A member lookup or update returns a 404
The address is not in that audience. Check that the audience id matches (run Mailchimp: List Audiences to list them), or use Mailchimp: Search Members to find which audience holds the contact. For write paths that should work either way, use the upsert node. Note that Mailchimp: Get Member returning a 404 is also the standard exists-check pattern, so in many workflows this response is information, not a failure.
The send node returns a 400
The campaign is missing content or complete settings. Run Mailchimp: Get Campaign to check its status and settings, set the body with Mailchimp: Set Campaign Content, and preview with Mailchimp: Send Test Email before retrying. If the campaign's status is no longer save, it has already been sent or scheduled and is past this step.
Scheduling a campaign rejects the send time
Mailchimp requires scheduled send times to fall on the quarter hour: minutes 00, 15, 30, or 45, in UTC. Round the time in the workflow before passing it to Mailchimp: Schedule Campaign (Sends Real Email at the Scheduled Time). To undo a schedule, Mailchimp: Unschedule Campaign returns the campaign to draft, but only until the send time arrives.
Canceling a send returns an error
Mailchimp: Cancel Campaign Send (Pro Only) is documented as included with Mailchimp Pro only, so other plans get an error, and it only applies while a campaign is actually sending. It is an emergency stop, not a planning tool: the reliable controls are gating the send nodes and using Mailchimp: Unschedule Campaign before a scheduled send time. A canceled send is permanent; the campaign cannot resume.
Nodes fail with a 429 when a workflow fans out
Mailchimp limits an account to 10 simultaneous API connections and returns a 429 beyond that, and its documentation states the limit is not raised per customer. Run loops serially rather than fanning out parallel branches, and page large reads with count and offset instead of launching many concurrent requests.

Mailchimp is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products