Offer configuration stays visible
Use Offers to decide what Drip receives: product, price, buyer, checkout mode, invoice, and automation context.
Product surfaces
Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before Drip receives checkout, payment, tax, or workflow context.
Use Offers to decide what Drip receives: product, price, buyer, checkout mode, invoice, and automation context.
Before Drip enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.
Drip should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.
Drip can start the sale through a hosted checkout, embedded checkout, modal, inline flow, or buy button depending on the stack.
Builder paths
Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.
Find full stack guides that pair Drip with checkout, payment, automation, fulfilment, records, and downstream integrations.
Use Offers to package products, prices, checkout pages, invoices, coupons, payment options, and follow-up context.
Use hosted checkout when Drip should hand the buyer to a branded Plandalf checkout page.
Use SDK checkout when Drip belongs inside an app, custom site, or API-first stack.
Route checkout events, purchase events, payment state, invoices, and customer context into another tool.
Turn a completed checkout into access, receipts, CRM updates, support context, and records.
Drip is an ecommerce-focused ESP with a workflow builder that includes a first-class Send an HTTP Post action. That action is the direct bridge to Plandalf: pick any subscriber event as the trigger, POST to the promo’s catch URL, done.
{{ subscriber.email }} tag
drops into the <img src> query string.Setup templates
Copy-paste setups for the most common ways to wire Drip into Plandalf.
promo · email
Paste this <img> tag into any email in Drip. {{ subscriber.email }}
is Drip's Liquid merge tag — Drip swaps it for the recipient's
address at send time.
<img
src="{{ promo.countdown_url }}?ref={{ subscriber.email }}"
alt="Time remaining on this offer"
/>
promo · automation
{{ promo.catch_url }}
application/json, body:
{"email": "{{ subscriber.email }}", "ref": "{{ subscriber.email }}"}
Automation graph
How Drip participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.
Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.
drip.subscriber_addeddrip.automation_step_reacheddrip.form_submittedThings Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.
drip.add_subscriberdrip.tagdrip.send_emaildrip.start_automationdrip.custom_api_callEmbeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution
trigger: stripe.payment_succeeded
actions:
- drip.add_subscriber:
list: paying-customers
tag: tier-${plan}
- plandalf.grant_entitlement: ${product_slug}Pair it with
Platforms whose roles complement Drip inside a Plandalf sequence.
Drip + ActiveCampaign
Capture a lead on ActiveCampaign, nurture it through Drip.
Drip + beehiiv
Capture a lead on beehiiv, nurture it through Drip.
Drip + Kit (ConvertKit)
Capture a lead on Kit (ConvertKit), nurture it through Drip.
Drip + Customer.io
Capture a lead on Customer.io, nurture it through Drip.
Drip + Flodesk
Capture a lead on Flodesk, nurture it through Drip.
Drip + Klaviyo
Capture a lead on Klaviyo, nurture it through Drip.
Integration methods
Each method below is the minimum viable setup. Pick the one closest to how you already use Drip with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.
Drop the Plandalf embed script into a Drip HTML block and tag any element with `data-plandalf-present` to open the configured flow on click.
<script src="https://cdn.plandalf.com/embed.js" async></script>
<button data-plandalf-present="offer_abc123">
Buy now
</button>Add an HTML block to any Drip email and paste the Plandalf countdown URL. Drip's merge tag `{{ subscriber.email }}` substitutes per recipient so each subscriber sees a timer pegged to their own deadline.
<img
src="https://cdn.plandalf.com/timers/{TIMER_ID}.gif?ref={{ subscriber.email }}"
alt="Time remaining on this offer"
width="600"
height="120"
/>Point a Drip form's webhook / POST URL at Plandalf's intake endpoint and every submission starts whatever sequence you've mapped to it.
curl -X POST https://api.plandalf.com/v1/intake/drip \
-H "Content-Type: application/json" \
-d '{"email": "{{ form.email }}", "source": "drip"}'Inside Drip's automation builder, add a Webhook step that POSTs the contact to a Plandalf sequence catch URL. Use this to mirror Drip journey logic into Plandalf without re-building the segmentation.
{
"email": "{{ contact.email }}",
"sequence": "post-signup-onboarding",
"source": "drip"
}For anything not covered by a native trigger, configure a Drip webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.
curl -X POST https://api.plandalf.com/v1/webhooks/drip \
-H "Authorization: Bearer $PLANDALF_API_KEY" \
-H "Content-Type: application/json" \
-d @event.jsonFAQ
Plandalf itself is free to connect. Drip's native webhook step is on its paid tiers — on the free plan, route the trigger through Zapier instead, which still works end-to-end.
Under 10 minutes. OAuth (or paste an API key), pick the lists/segments you care about, and you're live. No code unless you want it.
Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Drip's own records are untouched. You can reconnect any time and resume from the last seen event.
Plandalf stores the Drip contact ID and the events Plandalf fired against that contact. Email content stays in Drip; Plandalf doesn't mirror your audience or newsletter archive.
Use the generic `drip.custom_api_call` action or the inbound `drip.webhook` trigger. Anything Drip's REST API can do, a Plandalf sequence can drive.
Plandalf respects Drip's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.
Drip's homepage at https://www.drip.com links to their developer docs. For Plandalf-side questions about the Drip integration, see the Plandalf docs.