Mailchimp integration · Email marketing
Grow your Mailchimp audience, with consent.
SuperBot connects to Mailchimp with an API key and an audience ID. When a selected event includes an email, SuperBot adds that person to your audience as pending, so Mailchimp's double opt-in email asks them to confirm. People already in the audience keep their current status and get their name and phone updated.
- API key + audience ID
- SuperBot → Mailchimp (audience members, write)
- Free, Starter & Pro
How the Mailchimp integration works
Giving an email in a support chat is not the same as agreeing to marketing email. That is why new Mailchimp members from SuperBot start as pending: Mailchimp sends its confirmation email, and the person is subscribed only after they confirm.
Existing members are matched by email address. SuperBot updates their name and phone merge fields and leaves their subscription status exactly as it was — an unsubscribed person stays unsubscribed.
- New lead captured
- Form submitted
- New conversation started
- Conversation escalated to a human
Highlighted: the events most teams keep for this connector. You choose per connection.
What gets sent
| From SuperBot | In Mailchimp |
|---|---|
| email_address (matched by hash) | |
| First word of the name | FNAME |
| Rest of the name | LNAME |
| Phone | PHONE |
| — | status_if_new = pending |
Connect Mailchimp to SuperBot
- In Mailchimp, create an API key under Account → Extras → API keys. The datacenter suffix at the end (for example -us21) is part of the key — keep it.
- Find your audience ID under Audience → Settings → Audience name and defaults.
- In SuperBot, open Dashboard → Integrations, find Mailchimp, select Connect, and paste the API key and audience ID.
- Under “Send these events”, keep only the events you want this connection to receive. All four are ticked by default: new lead captured, form submitted, new conversation started, and conversation escalated to a human.
- Select “Connect & verify”. SuperBot reads the audience from Mailchimp to confirm the key and ID match before saving.
- Use “Send test” to push a sample contact ([email protected]) and check the result on the connection card.
Don't have a workspace yet? Sign up free — no card needed — then open Dashboard → Integrations.
Permissions and privacy
- Mailchimp API keys are account-wide rather than scoped, so create a dedicated key for SuperBot that you can revoke on its own.
- The key is encrypted before storage; the audience ID is stored as plain configuration.
- Only email, name, and phone are sent. No transcript, message, or company.
- Events without an email are skipped. Disconnect deletes the stored key.
What teams use Mailchimp with SuperBot for
- Newsletter sign-ups from support chats
Visitors who leave an email in chat receive Mailchimp's confirmation and join your list only if they want to.
- Cleaner member records
Existing subscribers who chat get their name and phone filled in without their subscription status changing.
- Form leads into one audience
SuperBot form submissions with an email go to the same audience as chat leads.
FAQ
Mailchimp integration questions, answered.
Ready to try it? Start free or compare plans. Every integration is on every plan.
Does SuperBot subscribe people to Mailchimp without consent?
No. New members are added as pending, which triggers Mailchimp's double opt-in email. They are subscribed only after they confirm.
What happens to people already in my audience?
They keep their current status. SuperBot only updates their first name, last name, and phone merge fields.
Why does SuperBot need my audience ID?
Mailchimp stores contacts per audience. The ID tells SuperBot which audience to add people to, and it is checked when you connect.
Can I use tags or groups?
Not from SuperBot directly. The Mailchimp connector writes email, name, and phone. For tags, route events through Zapier or your own webhook.
Is the Mailchimp integration free?
Yes. Every SuperBot integration works on Free, Starter, and Pro.