Mailchimp Webhook

Mailchimp Webhook is the entry point of a flow that starts with Mailchimp notifications. When someone subscribes to one of your lists, unsubscribes or updates their profile, Mailchimp notifies NappAI and the flow runs with that person’s details.

It is useful for reacting right away to changes in your audience without checking Mailchimp by hand.

When to use it

• Someone subscribes to your newsletter and you want to add them to your CRM too.
• A subscriber unsubscribes and you want to tell your sales team or flag them in your database.
• A subscriber changes their phone number or company in their profile and you want to copy the change to your other systems.

Configuration

This component does not need a credential: Mailchimp sends the notifications to an address of your own flow.

Field	What it does
Data	For testing the component in the editor: paste a sample Mailchimp notification here and run the flow. When the flow runs for real, this field is filled by the notification that arrives from Mailchimp.

Advanced options

Field	What it does
Store Messages	Saves the notification as a message in the conversation history, using the subscriber’s email as the conversation. On by default.

Connect Mailchimp to the flow

1. Deploy a version of the flow: Mailchimp notifications always run the deployed version. See Versions and publishing.
2. On the Mailchimp Webhook node, open its advanced settings and click Consume. The API access window opens on the Mailchimp Webhook tab.
3. Copy the address under Webhook URL.
4. In Mailchimp, open your audience settings, go to the webhooks section, create a new one and paste that address. Tick the notifications you want to receive: subscribes, unsubscribes, profile updates, email changes, cleaned addresses and sent campaigns.

Output

The component has two outputs:

• Data: the details of the notification, with its type (subscribe for a sign-up, unsubscribe for an unsubscribe, profile for a profile update, upemail for an email change, cleaned for an address Mailchimp cleaned or campaign for a sent campaign), the date, the list and the subscriber’s details: email, first name, last name, address, phone number, birthday and company. Details your audience does not have come empty, and merges holds every audience field Mailchimp sent. In upemail, email is the new address and old_email the previous one; in cleaned and unsubscribe, reason says why; in campaign, subject is the campaign subject.
• Message: a sentence describing what happened, for example New subscription from followed by the email. It works well connected to an agent or to a message for your team.

Example

A training school wants every new newsletter subscriber to appear in its CRM.

1. Create a flow with Mailchimp Webhook as the first component.
2. Connect the Data output to the CRM component that creates contacts, with the subscriber’s email, first name and last name.
3. Deploy the flow and connect Mailchimp following the steps in Connect Mailchimp to the flow.

Good practices

• Remember to deploy the flow again after changing it: until then, notifications keep running the previously deployed version.
• A flow can only have one webhook component.

Related components

• Member: look up and change the subscribers of your lists.
• Campaign: manage your campaigns.