CRM & data integration

Send form responses to Mailchimp

MA

Paste a Mailchimp API key and audience ID into your form to subscribe respondents as they submit. Status defaults to pending, so double opt-in stays intact unless you choose otherwise.

What the Mailchimp integration does

  • Defaults to pending status for double opt-in compliance; set subscribed when you have explicit consent.
  • Uses your own API key, tied to your data centre suffix.
  • Rejected addresses appear in the delivery log with Mailchimp's reason.

What it looks like

A Mailchimp audience member with the email and merge fields it can match.

HelloForms — response

Removals enquiry · #4821

Full name
Priya Raman
Email
priya@northgate.co
Service needed
Office move
Budget
£2,000 – £5,000

Mailchimp — record created

Priya Raman

Created from Removals enquiry · #4821

Full name
Priya Raman
Email
priya@northgate.co
Service needed
Office move
Budget
£2,000 – £5,000
Demo data: a HelloForms response on the left, and how it arrives in Mailchimp on the right.

How to connect Mailchimp to your form

  1. 1

    Copy an API key from Account → Extras → API keys.

  2. 2

    Copy the audience ID from Audience → Settings → Audience name and defaults.

  3. 3

    Only send marketing email to people who agreed — use pending for double opt-in.

What you’ll need

  • Mailchimp API key.
  • Audience (list) ID
  • Subscribe status (optional) — Use pending for double opt-in. Defaults to pending.

Credentials are stored server-side and never rendered in your published form. Every delivery attempt is logged, transient failures are retried with backoff, and repeated failures disable the destination instead of retrying forever.

Configuration template and sample payload

Download a filled-in checklist of every value the Mailchimp destination asks for, plus an example of exactly what Mailchimp receives for one submission — useful for planning a mapping or handing the setup to a developer.

Every field the "Add integration" dialog asks for, with placeholders to fill in. Keep it as documentation of your Mailchimp mapping — do not commit a completed copy to a public repository.

{
  "$schema": "https://helloforms.net/integrations/config-template.schema.json",
  "helloforms": {
    "destination": "mailchimp",
    "label": "Mailchimp",
    "docs": "https://helloforms.net/integrations/mailchimp"
  },
  "enabled": true,
  "events": [
    "submission.created"
  ],
  "credential": {
    "label": "Mailchimp API key",
    "value": "<paste-your-token-here>"
  },
  "config": {
    "listId": "a1b2c3d4e5",
    "status": "subscribed or pending"
  },
  "includedQuestions": [
    "Full name",
    "Email",
    "How can we help?"
  ],
  "notes": [
    "Never commit a filled-in copy of this file to a public repository.",
    "Values are entered in HelloForms → your form → Integrations; this file is a checklist and a record of your mapping."
  ]
}

Mailchimp integration FAQs

Who uses it

  • Newsletter signup forms embedded on a marketing site.
  • Lead magnets where the download and the list subscription happen together.
  • Event forms that build a follow-up audience for the next campaign.

Build a form that feeds Mailchimp today

Every destination is included on every plan — no per-integration add-ons.