Native integration

Mailchimp + Drip integration

Mailchimp and Drip both have built-in Plandalf steps, so one checkout can fill both while you move your automations across.

No credit card required. No coding required.

Does Mailchimp integrate with Drip?

Plandalf does not sync Mailchimp with Drip, but it has native steps for both, so a single sequence can write the buyer to each. Contact Subscribed in Mailchimp and Tag Applied in Drip can each start a sequence that passes the person to the other tool.

What moves between Mailchimp and Drip

EventFrom and toThroughWhat happens
Checkout completedPlandalfMailchimpNative stepAdd or Update Contact with a status for new contacts, then Add Tags to Contact. Record Event starts a Customer Journey but carries no revenue.
Checkout completedPlandalfDripNative stepCreate or Update Subscriber, Apply Tag and Record Event in the same sequence. Give the event a value property set to {{trigger.total}}, which is already in cents, and Drip counts it as revenue.
Contact subscribedMailchimpDripNative stepThe trigger starts a sequence that runs Create or Update Subscriber and Apply Tag in Drip, so people who join the Mailchimp audience reach Drip without a manual export.
Tag appliedDripMailchimpNative stepPick a Tag on the Drip trigger to fire for one tag only. The sequence then runs Add Tags to Contact in Mailchimp for the subscriber's email.
Invoice refundedPlandalfMailchimpNative stepRemove access on refund adds Remove Tags from Contact for Mailchimp and Remove Tag for Drip into one sequence, each already pointed at {{trigger.customer_email}}.

Fill Mailchimp and Drip together while you migrate

Connect both accounts first: a Mailchimp API key with its suffix, and a Drip API token plus the numeric Account ID.

  1. Connect both apps

    In Automation, then Marketplace, connect Mailchimp and Drip. For Drip, paste the token from User Settings and the Account ID from Account settings, then wait for Drip connected.

  2. Create one sequence for the checkout

    Under My Sequences, choose Plandalf and Checkout Completed, pick the offer, and select a recent checkout as the sample on the Test tab.

  3. Write to Mailchimp

    Add Mailchimp, Add or Update Contact, and a tag step with the product name. Leave Status for New Contacts on Subscribed only if your checkout asks for marketing consent.

  4. Write to Drip with revenue

    Add Drip, Create or Update Subscriber, then Record Event named exactly as your Drip workflow expects. Add product and value event properties.

  5. Add the refund sequence

    Add the Remove access on refund template for the same checkout and pick the Mailchimp tags and the Drip tag. Keep Full refunds only on so a goodwill partial refund leaves both tags alone.

  6. Retire Mailchimp when ready

    Once the Drip workflows send what the Customer Journeys did, delete the Mailchimp steps from the sequence. Nothing else in the sequence changes.

What sellers do with Mailchimp and Drip

Moving a ticketed event list from Mailchimp to Drip

Ticket buyers are tagged in Mailchimp for the old reminder journey and recorded in Drip as an event with revenue for the new workflow. Both reminders can run until you switch the old one off.

Keeping a Mailchimp audience for the newsletter and Drip for buyers

Some sellers never fully leave Mailchimp. Tagging there keeps the newsletter segments honest, while Drip carries the revenue events and purchase workflows.

Limits and gotchas

  • Mailchimp's triggers fire whoever changed the audience, Plandalf included. A sequence that adds buyers to an audience will therefore also start any sequence listening to Contact Subscribed on it.
  • Drip's rate limit is 3,600 requests an hour per account, and it refuses two changes to the same subscriber at once, so keep the Drip steps in one sequence rather than several that fire together.
  • Drip counts revenue from the value event property, in cents. Mailchimp events carry none, so the order total has to travel as an event property or a merge field.
  • Drip has other webhook events, such as email opens and clicks, that Plandalf has no triggers for.
  • Plandalf will not copy your existing contacts from one tool to the other. Only people who buy or subscribe after the sequence is on are written.

Mailchimp and Drip: common questions

Does Mailchimp integrate with Drip?
Not directly through Plandalf, which does not sync the two. It has native steps for each, so one checkout can write the buyer to both, and a subscribe or tag in one tool can start a sequence that updates the other.
How do I connect Mailchimp to Drip?
Connect each under Automation, then Marketplace. Build a sequence on Checkout Completed with a Mailchimp step and a Drip step, or start from a Mailchimp or Drip trigger to mirror subscribers.
Can I migrate from Mailchimp to Drip using Plandalf?
It helps with the overlap. New buyers go into both tools while you rebuild automations in Drip. Importing the existing list is done in Drip itself.
Where does the order total go in each tool?
In Drip, put it in the value event property in cents. In Mailchimp, which does not accept revenue on events, put it in an event property or a merge field.

Feature detail