Three Mailchimp triggers start a run the moment one of your audiences changes:

  • Mailchimp · New subscriber — When someone subscribes to an audience.
  • Mailchimp · Unsubscribed — When someone unsubscribes from an audience.
  • Mailchimp · Profile updated — When a subscriber's details change in an audience.

They are instant triggers. Publishing makes the webhook on the audience in Mailchimp for you, and nothing needs pasting — see How instant triggers work.

Who can do this

Workspace Admins and Editors, on every plan — Mailchimp is not a premium connection. Viewers see the trigger and its status but cannot change it.

Before you start

A Mailchimp connection — see Connect Mailchimp.

Steps

  1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.

  2. Under Mailchimp, select New subscriber, Unsubscribed or Profile updated — each reads Mailchimp · instant. Or type Mailchimp in Search triggers.

  3. In Connection, choose your Mailchimp connection — for example Consulace Mailchimp.

  4. In Audience, choose the audience. It must be chosen before you can publish.

  5. The panel reads Publishing sets this up in Mailchimp; unpublishing takes it away. It starts with what happens after that.

  6. Add the steps, then Publish. Bizomate makes a webhook on the audience in Mailchimp for that one change, from every source — a sign-up form, someone in Mailchimp, or the API.

    The panel reads Waiting for the first event — Make one happen; it appears here within seconds.

Test with a real change:

  1. Subscribe a test address to the audience — rohan@consulace.com through your sign-up form, say — or unsubscribe it, or change its name, to match the trigger.
  2. Within seconds the panel reads Listening — instant — Last event 10:45 · New subscriber · rohan@consulace.com.
  3. On Output, select Use the last event, then Test run.

What the trigger gives

Each change is one item:

Field What it is
email The subscriber's address — rohan@consulace.com.
id Mailchimp's id for the subscriber.
listId The audience's id.
firedAt When it happened, as Mailchimp gives it — 2026-10-02 09:30:00.
merges The subscriber's merge fields, by their tag — {{ trigger.merges.FNAME }} is the first name, {{ trigger.merges.LNAME }} the last.
reason For Unsubscribed, why, when Mailchimp says.

Use them in later steps as {{ trigger.email }} and so on.

What happens next

  • Each change starts one run of the live version, in Production, named after it — Unsubscribed · rohan@consulace.com.
  • Changing the audience or the connection and publishing deletes Bizomate's old webhook in Mailchimp and makes one on the new audience.
  • Changing to another trigger and publishing, or deleting the workflow, deletes the webhook in Mailchimp.

Good to know

  • Each workflow has its own webhook on the audience. You can see them in Mailchimp under the audience's settings, on its webhooks page. Leave them be: deleted in Mailchimp, the trigger hears nothing, and Bizomate does not notice.
  • Changes made through the API count too — including Bizomate's own Mailchimp steps. A workflow on Profile updated that updates the same subscriber starts itself again; give it a condition that stops it.
  • With double opt-in, Mailchimp counts someone as subscribed only once they confirm, so New subscriber comes then.
  • Mailchimp checks the address before it makes the webhook, by calling it once; Bizomate answers. Nothing runs from that check.
  • Mailchimp does not sign its calls. The 48-character code in the address is the secret.

If something goes wrong

What you see Why What to do
Not listening — Mailchimp would not take Bizomate's address: Mailchimp refused: … Check the connection's details on Connections. Fix it, then publish again. The API key was revoked in Mailchimp. Select Reconnect, paste a new API key, then publish again.
Not listening — … Mailchimp refused: … Fix it, then publish again. naming the audience The audience was deleted, or belongs to another account. Choose the audience again, then publish.
Not listening — … Choose the audience. … Audience is empty. Choose one, then publish.
Not listening — … Mailchimp made the webhook but gave no id for it. … Mailchimp answered without the webhook's id. Publish again.
Waiting for the first event stays Nothing has changed in the audience yet, or the webhook was deleted in Mailchimp. Make a change in the audience. If the webhook is gone, choose another audience and publish, then choose this one again and publish.