LanguageENES
MailchimpAvailable on Starter

Add chatbot leads to a Mailchimp audience

Subscribed with the tags you decide

Leads go to the audience you pick, with merge fields mapped and tags applied, so a question asked at midnight can start the sequence you already wrote.

What it does

Merge fields, not just the email

First name, company, whatever your audience defines. We read the merge fields so the mapping is against what exists.

Tagged on arrival

Tag by route, and a route is scoped to a widget -- so the newsletter widget and the demo widget are told apart in Mailchimp, or land in different audiences entirely.

Consent stays yours

The subscriber status we send is the one you choose, so a double opt-in audience keeps behaving like one.

How to connect it

Read the full guide
  1. 1

    Create a Mailchimp API key

    Account, Extras, API keys. The key carries its own data centre prefix, which is all we need to reach your account.

  2. 2

    Connect Mailchimp

    In Destinations, paste the key and pick the audience.

  3. 3

    Create a route

    Choose which leads it takes -- one widget, or all of them -- and the tags to apply.

  4. 4

    Map the merge fields

    Auto-map, then check it. The dispatch log keeps every attempt.

Questions people ask

Will it overwrite an existing subscriber?

It updates them by email. Fields with nothing behind them are left out rather than blanking what you already had.

Can I use double opt-in?

Yes. You choose the status we send, so the audience keeps whatever consent flow you set up.

What about unsubscribes?

They are Mailchimp's to manage. We never resubscribe someone who opted out.

What teams use it for