Drip

Integration

Drip

Plandalf integrates with Drip as a email, marketing, website, sdk platform.

What it does

Product surfaces

Where Drip fits in the buying workflow

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.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.
The Numi checkout elements palette showing content, interactive, and selling blocks.
The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

Drip should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.

The Numi offer editor showing hosted checkout mode controls.

Builder paths

Stack guides that use Drip

Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.

Overview

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.

What Plandalf does here

  • Countdown in emails — Drip’s Liquid {{ subscriber.email }} tag drops into the <img src> query string.
  • HTTP-Post-driven enrolment — no middleware required; Drip speaks JSON natively in Workflow actions.

Setup templates

Drop-in implementations

Copy-paste setups for the most common ways to wire Drip into Plandalf.

promo · email

Drop the Plandalf countdown image into a Drip 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

Enrol Drip subscribers via a Workflow

  1. In Drip, go to Automation → Workflows → New workflow.
  2. Pick a start trigger — Applied tag, Subscribed to your account, or Submitted form are the usual fits.
  3. Add an action: Send an HTTP Post.
  4. URL:
    {{ promo.catch_url }}
    
  5. Content type application/json, body:
    {"email": "{{ subscriber.email }}", "ref": "{{ subscriber.email }}"}
    
  6. Start the workflow.

Automation graph

Connecting Drip

How Drip participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.

Triggers from Drip

Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.

drip.subscriber_added
Fires when a new subscriber is added to Drip.
drip.automation_step_reached
Fires when a contact reaches a designated step in a Drip automation.
drip.form_submitted
Fires when a form on Drip is submitted.
drip.webhook
Fires when Drip POSTs to a Plandalf webhook URL — use for anything not covered by a native trigger.

Actions on Drip

Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.

drip.add_subscriber
Add a contact to a list or audience in Drip.
drip.tag
Apply a tag or segment to an existing Drip contact.
drip.send_email
Send a one-off transactional or broadcast email through Drip.
drip.start_automation
Enrol a contact into a Drip automation.
drip.custom_api_call
Hit any Drip REST endpoint with a templated payload.

Embeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution

Example sequence
trigger: stripe.payment_succeeded
actions:
  - drip.add_subscriber:
      list: paying-customers
      tag: tier-${plan}
  - plandalf.grant_entitlement: ${product_slug}

Integration methods

How Drip connects to Plandalf

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.

  1. Method 1

    Embed a Plandalf buy button

    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>
  2. Method 2

    Drop in a per-recipient countdown image

    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"
    />
  3. Method 3

    Trigger a sequence from a form

    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"}'
  4. Method 4

    Enrol from an automation step

    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"
    }
  5. Method 5

    REST API webhook

    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.json
Official Drip docs and sign-up: www.drip.com

FAQ

Common questions about the Drip integration

Do I need a paid plan to use Drip with Plandalf?

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.

How long does setup take?

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.

Can I disconnect Drip later without losing data?

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.

Does Plandalf store Drip data?

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.

What if my email need isn't covered by the actions or triggers listed here?

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.

Is there a usage limit?

Plandalf respects Drip's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.

Where do I find Drip's own documentation?

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.

Feature detail