Stripe + Drip integration

Plandalf connects them with native Drip steps and no direct Stripe-to-Drip sync. Stripe takes the payment in a Plandalf checkout, then a sequence creates or updates the Drip subscriber, applies a tag and records a custom event that can carry the amount as revenue. Drip events such as a tag being applied can start Plandalf sequences.

1. Connect Stripe and publish the checkout

   Authorize your Stripe account in Plandalf, attach a Stripe-backed price to the offer for your product and publish it. Payments run through Stripe and settle in your Stripe account.

2. Copy the Drip token and account ID

   In Drip open Settings, then User Settings, and copy the API Token from the User Info tab. Then open Settings, then Account, and copy the Account ID under General Info, which is a number and not the account name. The token belongs to your Drip user, so a new token stops the old one working.

3. Connect Drip

   In Plandalf go to Automation, then Marketplace, and click Connect on Drip. Paste the API Token and Account ID. Plandalf loads the account to check both and shows Drip connected.

4. Tag the buyer

   Create Ticket buyers to Drip under My Sequences, choose Plandalf, Checkout Completed and your checkout under Offer. Add Drip, Apply Tag with Email Address {{trigger.customer_email}}, a tag such as Retain Live 2027 and First Name {{trigger.customer_first_name}}.

5. Record the purchase

   Add Drip, Record Event with the same email and Event Name Bought Retain Live ticket. Add the Event Properties product as {{trigger.line_items_summary}} and value as {{trigger.total}}.

6. Start the workflow in Drip

   In Drip build a workflow that starts when a subscriber performs that custom event, spelled the same way, and add the emails. Then, in Plandalf, add Remove access on refund for the checkout and pick the tag in its Remove Tag step.

7. Test with a Stripe test card

   Switch on Run on test purchases, pay through the test link with a Stripe test card, and watch the subscriber in Drip, then switch it off. A step test changes the real subscriber, so use your own email.

• Purchases reach Drip as custom events, not orders or products. Plandalf has no Drip order API step, so segment on the event name, its properties and tags.
• Drip matches workflow triggers on the exact event name. A different spelling in the Record Event step means the workflow never starts.
• Removing the tag on refund does not undo a recorded event or its value. Plandalf has no step that deletes a Drip event, so revenue already recorded stays.
• The API token belongs to your Drip user. Generating a new token breaks the connection until you paste the new one into the connection under My apps.
• Drip allows 3,600 requests an hour per account and refuses two changes to the same subscriber at the same moment. Plandalf retries twice, then you re-run the step.
• Plandalf has no subscription-cancelled trigger, so a cancelled plan keeps its tag until you remove it in Drip.

Does Stripe integrate with Drip?

Through Plandalf. Stripe takes the payment in a Plandalf checkout and a sequence then tags the buyer in Drip and records a purchase event. For Drip's own ecommerce connections, check Drip's integrations list.

How do I connect Stripe to Drip?

Connect Stripe to Plandalf and publish a checkout, then connect Drip under Automation, then Marketplace, with your API token and account ID. A sequence that starts on Checkout Completed runs Apply Tag and Record Event.

How do I send Stripe sales to Drip as revenue?

Add a value event property set to {{trigger.total}} in the Record Event step. The total is already in cents, which is what Drip expects, and the sale appears as an event rather than as a Drip order.

Will a Stripe refund remove the buyer's tag in Drip?

Yes, once a full refund succeeds in Stripe, including from the Stripe dashboard. The Remove access on refund template runs Remove Tag for the tag you pick.

Checked October 26, 2026 against Plandalf's own setup guides.