Mailchimp Campaign Report

Summarize recent Mailchimp campaign performance and deliver a digest to your InTouch subscribers.

Use case

Marketing teams send email campaigns through Mailchimp but rarely log into the dashboard to review how each one performed. This workflow pulls the most recent sent campaigns and their report summaries (opens, open rate, clicks, click rate, unsubscribes) and pushes a concise digest to the people who care — over whatever channels they're subscribed on (email, Slack, Discord, Telegram, etc.).

Schedule it weekly (e.g. Monday morning) to start the week with a read on what landed and what didn't.

What it does each run

1. fetch-campaigns (mailchimp connector) — calls the Mailchimp API with operation: list-campaigns (status sent, newest first, up to 10). Like every InTouch connector tool it takes apiKey + operation + operation-specific params, and publishes exactly two outputs: - {{fetch-campaigns.result}} — the raw Mailchimp JSON response (a string) - {{fetch-campaigns.status}} — the HTTP status code
2. build-digest (runtimeenv) — a small Python step that receives {{fetch-campaigns.result}} via an environment variable, parses the campaigns[] array and each campaign's report_summary, and prints a human-readable digest. Its text is published as {{build-digest.output}}.
3. notify (message) — sends {{build-digest.output}} (plus the API HTTP status) to the workflow's contacts as an InTouch notification.

If the Mailchimp fetch fails, the intouch user is alerted via the alertOnError notification.

Required credentials

Mailchimp API key

The mailchimp connector authenticates with a static Mailchimp API key. You supply it — the workflow ships with the apiKey property set to the placeholder <set via credential> and never hardcodes a key.

Two ways to provide it:

• Credential (recommended) — create a Mailchimp-type credential in Connections and attach it to the fetch-campaigns task. The connector reads the key from the credential vault; it is never exposed to AI context.
• Runtime environment — store the key as a runtime-env variable and reference it from the apiKey property.

Generate the key in Mailchimp under Account → Extras → API keys. The data center is the suffix of the key (e.g. ...-us21 → us21) and is used as the API host; most Mailchimp connector builds derive it automatically from the key.

No OAuth flow is required, so this workflow runs unattended once the key is saved.

Subscribers

Add one or more subscribers to this workflow (or link an alert) so the notify step has somewhere to deliver. Without subscribers the digest is generated but goes nowhere.

Tuning

• count — number of recent campaigns to include (default 10).
• status — set to sent to only report on delivered campaigns (default).