When a new form is submitted in Webapi.ai, add or update the contact in Mailchimp

Each Webapi.ai form response adds the person to your Mailchimp audience, or updates their details if the address is already on the list.

Webapi.ai

Mailchimp

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.3k sites Free to import

What this workflow does

Webapi.ai forms and chat flows collect contact details from visitors who want to hear back from you. If those details stay inside Webapi.ai, your newsletter never reaches them. This workflow passes each response to Mailchimp so the person joins your email list.

A run begins each time Webapi.ai receives a response to your form. The Mailchimp step, Add New Member, then adds the person to the audience you choose. FlowMattic describes it as adding a new member, or updating them if they already exist, so a returning visitor's record is refreshed instead of duplicated.

Nothing in the Mailchimp step is set yet. After import, choose the audience and map the email from the Webapi.ai response, plus any name or merge fields you collect. Every response runs the step, so think about consent: only send people who agreed to hear from you, and check in a test how Mailchimp records their status.

Submit a test response with your own address, then look for it in the Mailchimp audience and check Task History for the reply Mailchimp sent.

Chatbot leads into a nurture list

A software company's Webapi.ai demo request form collects leads, and each visitor's email joins the Mailchimp audience that receives product updates.

Event interest form

A conference organiser collects early interest through a Webapi.ai form and emails the whole audience when tickets open.

Keeping returning visitors current

A visitor who fills in the form again with a new name or company has their existing Mailchimp record updated, not a second one added.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Webapi.ai New Form Submission
Starts the workflow when a Webapi.ai form response is received. The answers, such as the visitor's email and name, are passed on for mapping into Mailchimp.
Step 2Action
Mailchimp Add New Member
Adds the person to the Mailchimp audience you choose, or updates them if the address is already there. Nothing is mapped in the template, so pick the audience and map the email and other fields after import.

What you need

FlowMatticCore
Webapi.ai AccountAccount
Mailchimp AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Add a consent question to the Webapi.ai form and a Filter between the Webapi.ai trigger and the Mailchimp step that continues only when it is answered yes.
Create a Mailchimp merge field for the source and map a fixed value such as Webapi.ai into it, so you can segment these sign-ups later.
Make the email question required in Webapi.ai, since Mailchimp needs an address to add or update a member.
Add a Slack step after the Mailchimp step to tell your sales team about each new Webapi.ai response as it lands.

Questions about this workflow

What if the Webapi.ai visitor is already in my Mailchimp audience?

Add New Member updates existing members instead of adding a second copy. The fields you mapped are refreshed from the new response.

Which Mailchimp audience do people join?

Whichever audience you select in Add New Member once the template is imported. To send different forms to different audiences, duplicate the workflow and pick another audience in each copy.

Are the Webapi.ai answers already mapped to Mailchimp fields?

No. The step ships unmapped, so you map the email and any name or merge fields yourself. Run a test to see the field names Webapi.ai sends.