Native on one side, webhook on the other
One Plandalf checkout tags the buyer in Mailchimp with a built-in step and adds them to ActiveCampaign through a webhook call.
No credit card required. No coding required.
Mailchimp
ActiveCampaignPlandalf does not sync contacts between Mailchimp and ActiveCampaign. What it does is run both from one purchase: native Mailchimp steps tag the buyer, and a Send Webhook step calls ActiveCampaign's contact API. A Mailchimp subscribe can also start a sequence that passes the contact on.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf → Mailchimp | Native step | Add or Update Contact and Add Tags to Contact, both with Email Address set to {{trigger.customer_email}}. A Record Event step can start a Customer Journey for the same buyer. |
| Checkout completed | Plandalf → ActiveCampaign | Webhook | A Send Webhook step posts to ActiveCampaign's contact sync endpoint on your account's api-us1.com address, with the key in an Api-Token header. ActiveCampaign finds the contact by email and changes only the fields you send. |
| Contact subscribed | Mailchimp → ActiveCampaign | Webhook | Plandalf's Mailchimp trigger starts the sequence and adds the audience webhook for you. The sequence's Send Webhook step makes the same contact sync call, so a new audience member also lands in ActiveCampaign. |
| Automation webhook | ActiveCampaign → Plandalf | Webhook | An ActiveCampaign automation can post to a Plandalf Webhook Trigger catch URL. Plandalf's own ActiveCampaign page says that payload is form-encoded with the email under contact[email], so check the Test tab shows the email before you map it. |
| Invoice refunded | Plandalf → Mailchimp | Native step | The Remove access on refund template removes the Mailchimp tag. Plandalf has no ActiveCampaign step, so taking a tag back there would be a second Send Webhook call that you build against ActiveCampaign's API. |
You need a Mailchimp API key with its data-centre suffix and an ActiveCampaign API key plus your account's API address.
In Plandalf open Automation, then Marketplace, and connect Mailchimp under Available now. Paste the whole key, including the part after the dash such as -us21, because Plandalf needs it to find your account.
Take your account name and API key from ActiveCampaign's developer settings. The contact sync address has the form https://youraccountname.api-us1.com/api/3/contact/sync and the key goes in a header called Api-Token.
Under My Sequences create a sequence, choose Plandalf and Checkout Completed, and pick the offer. On the Test tab choose a recent checkout so the variable menu fills in.
Add Mailchimp, Add or Update Contact with your audience and {{trigger.customer_email}}, then Add Tags to Contact with a tag that names what was bought.
Add Plandalf, Send Webhook. Set the URL to the sync address, the method to POST and a header Api-Token holding your key. In the JSON payload send a contact object with email, firstName and lastName filled from the trigger variables.
Run the step's test and read the status code in its output: ActiveCampaign documents 200 for an update and 201 for a new contact. Then switch on Run on test purchases, buy through the test link with your own email, and check both tools.
A consultant sells a paid workshop. The buyer gets a Mailchimp tag so the monthly newsletter can treat them as a customer, and the same checkout writes them to ActiveCampaign, where the sales follow-up automations already live.
A team shifting its email from Mailchimp to ActiveCampaign keeps new buyers flowing into both while the old Customer Journeys finish. Once the last journey is retired, delete the Mailchimp steps and keep the webhook step.
When an ActiveCampaign automation posts to a catch URL, a Plandalf sequence adds the matching Mailchimp tag, so a campaign aimed at that tag reaches the same people.
Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: ActiveCampaign API: sync a contact's data.
