Mailchimp Trigger
Triggers a workflow on Mailchimp audience events (subscribe, unsubscribe, profile update, email cleaned, campaign sent). Webhooks are automatically registered with Mailchimp on publish.
Requires a Mailchimp connection.
Configuration
| Field | Description | Notes |
|---|---|---|
| Connection | Mailchimp connection | Required |
| Audience (List) ID | The Mailchimp audience to watch | Required. Find under Audience → Settings → Audience name and defaults |
| Events | Subscribe / unsubscribe / profile / cleaned / upemail / campaign | At least one required |
Output
Mailchimp sends webhooks as application/x-www-form-urlencoded payloads. The backend parses them into a structured object:
| Field | Description |
|---|---|
body.type | The event type (subscribe, unsubscribe, etc.) |
body.fired_at | When the event happened |
body.data | Event-specific data (member details, campaign info, etc.) |
How It Works
- On publish, the backend calls Mailchimp's Add Webhook endpoint with the configured audience, events, and your workflow's public URL.
- Mailchimp delivers events to the URL.
- On unpublish/delete the webhook is removed.
Security
No Signature Scheme
Mailchimp does not sign webhook payloads. Authentication relies entirely on the unguessable URL token embedded in your workflow's webhook path. Treat that URL like a credential — anyone who knows it can forge events.