Use case: we want to connect MailChimp to Corezoid in order to build automations based on a new subscriber event. For example, send them welcome email series or sync them with another database.
Problem: MailChimp sends webhooks not in JSON format that is supported by Corezoid.
Solution: use Zapier which is already connected to Mailchimp to send JSON webhooks to Corezoid.
Zapier currently supports these MailChimp triggers:
- New Campaign
- New Cleaned Subscriber
- New List
- New Bounce
- New Subscriber
- New Group
- New Unsubscriber
- Updated Subscriber
In order to sync our mailing list with Corezoid, we’ll need only ‘New Subscriber’, ‘New Unsubscriber’ and ‘New Cleaned Subscriber’. If we have groups that can be updated by the user, we’ll also have to use ‘ Updated Subscriber’ trigger. We’ll need to create a separate zap for each of these events.
I’ll show you, how to build a zap for the New Subscriber trigger and make Zapier send a POST webhook to our Corezoid process.
Building MailChimp to Corezoid Zap
1. Create a new zap
2. Select you MailChimp account
3. Choose a list
4. Create a new Corezoid Process
Let’s leave our unfinished zap alone for a second to open Corezoid in a new tab. Create a new process in your Corezoid admin and copy to clipboard it’s direct upload URL.
5. Match up MailChimp Subscriber to Webhooks by Zapier POST
Get back to Zapier and paste that URL into URL field on step 5.
Also chose JSON as zap’s Payload Type (basically it’s just webhook format which Zapier will use)
Leave all other fields at this stage unchanged and press ‘Continue’.
6. Test your Zap
If your MailChimp list already has got some subscribers, you’ll be able to test your newly created zap. Push the button ‘Test Zap with this sample’ and go to Corezoid.
Switch to Dashboard view in Corezoid and open your MailChimp process. You’ll notice how the number of tasks in process’ final node changes in a second after you send it your sample subscriber. Open tasks archive (left mouse click on the final node) and see what data you have.
If you can see new subscribers coming into your process, you can start building your automated workflow right away. But in order to create a completely synced process, you’ll have to build additional zaps for unsubscribers and cleaned emails and a separate Corezoid process that will be deleting unsubscribers from your first process. I’ll explain how to do this in another post.