Skip to main content

Prerequisites

Before continuing, you should have already completed the following for this connector:
1

Configure the Connector

Enable the connector and set up its connector profile in your project. See Managing Connectors.
https://stackone-logos.com/api/mailchimp/filled/png

Connector Profile

Mailchimp - OAuth 2.0
https://stackone-logos.com/api/mailchimp/filled/png

Connector Profile

Mailchimp - API Key
2

Link an Account

Connect an account using StackOne Hub or Auth Link.
https://stackone-logos.com/api/mailchimp/filled/png

Link Account

Mailchimp - OAuth 2.0
https://stackone-logos.com/api/mailchimp/filled/png

Link Account

Mailchimp - API Key

Subscribe via the StackOne dashboard

This connector uses Programmatic Webhooks. When you enable webhook events for a connected Mailchimp account, StackOne automatically registers a webhook on each configured audience (via POST /lists/{list_id}/webhooks), subscribed to all audience events from all sources (user, admin, and API).

1

Set the Webhook Audience ID

In the connection’s configuration, set Webhook Audience ID to the ID of the Mailchimp audience you want events from — or several as comma-separated IDs (e.g. a6b5da1054 or a6b5da1054,f7c8eb2165). A webhook is registered on each audience.

  • Find audience IDs in Mailchimp under AudienceSettingsAudience name and defaults (the Audience ID field), or by calling the connector’s list_audiences action.
  • Enter the IDs without spaces around the commas.
2

Select event subscriptions in the dashboard

In the StackOne dashboard, open the Mailchimp connector profile and enable the webhook events you want delivered downstream. See the Available Webhook Events section below for the full list.

3

Connect the Mailchimp account

On account connection (or when event subscriptions change), StackOne registers a webhook on each configured audience on your behalf using the connected account’s credentials. Mailchimp verifies the endpoint when each webhook is created; StackOne answers the verification automatically.

4

Verify delivery

Trigger a matching change in Mailchimp (for example, subscribe a test contact to the audience) and confirm the event reaches your downstream consumer.

  • Mailchimp sends events as form-encoded HTTP POSTs; StackOne responds with 200 OK automatically.
  • If the endpoint is unavailable or takes more than 10 seconds to respond, Mailchimp retries at increasing intervals over 75 minutes, and may disable webhooks that keep failing.
5

Receive events from additional audiences

To receive events from more audiences, append their IDs to the Webhook Audience ID field (comma-separated). Avoid editing the field while webhooks are registered — the stored registration is paired with the audience list at creation time, so unsubscribe first, update the IDs, then re-subscribe. Webhooks orphaned by an out-of-sync edit can be removed in Mailchimp under AudienceAudience settingsManage webhooks.

6

Unsubscribe

Changing your event selection re-registers the StackOne-managed webhooks. Disconnecting the account deletes them from every configured audience, stopping deliveries.

Available Webhook Events

The following Mailchimp audience events can be enabled. The StackOne-managed webhooks are subscribed to all six event types in Mailchimp; only events enabled in StackOne are delivered downstream.

1

Contact events

Events related to contacts on the audience.

  • Email Subscribed (subscribe) — Fired when a contact subscribes to the audience
  • Email Unsubscribed (unsubscribe) — Fired when a contact unsubscribes or is removed
  • Profile Updated (profile) — Fired when a subscriber’s profile is updated
  • Email Address Changed (upemail) — Fired when a subscriber changes their email address
  • Email Cleaned (cleaned) — Fired when an address is cleaned from the audience (hard bounce or abuse complaint)
2

Campaign events

Events related to campaign sending.

  • Campaign Sent (campaign) — Fired when a campaign to the audience finishes sending or is cancelled

Delivery format

Details of how Mailchimp delivers events to StackOne.

1

Form-encoded payloads

Mailchimp delivers each event as an HTTP POST with an application/x-www-form-urlencoded body — a type field, a fired_at timestamp, and the event details under data.

Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.