---
description: "Connect Drip to Plandalf with an API token and account ID, then add buyers as subscribers, tag them, record purchase events that start Drip workflows, and remove tags on refund."
---
# Drip setup

Connect your Drip account so your Plandalf automations can act on your subscribers. When someone buys, a sequence can add them to Drip, apply a tag for what they bought, and record a custom event such as “Bought Retain Live ticket” that a Drip workflow starts from. When they’re refunded, another sequence can remove the tag again. Drip events, such as a new subscriber or a tag being applied, can also start a Plandalf sequence.

## Before you start

-   A Drip account, and a Drip user who can see **User Settings** and **Account** settings.
-   The tags and custom fields you plan to use. The Apply Tag step can also create new tags for you, and Drip creates a custom field the first time a value is sent for it.
-   A Plandalf checkout to connect it to, if you want purchases to reach Drip.

## Get your Drip API token and account ID

Plandalf needs two things from Drip: your personal API token and the ID of the Drip account to connect.

1.  [Copy your API token](#copy-drip-api-token)

    Log in to Drip. Open **Settings**, choose **User Settings**, and copy the **API Token** from the **User Info** tab. The token belongs to your Drip user, so if you generate a new one, the old one stops working and you will need to update the connection in Plandalf.

2.  [Copy your account ID](#copy-drip-account-id)

    Open **Settings**, choose **Account**, and copy the **Account ID** under **General Info**. It is a number, usually seven digits. You can also read it from your browser’s address bar while you’re logged in to Drip: it is the number straight after `getdrip.com/`.

If you have more than one Drip account, use the ID of the one you want Plandalf to write to. Your API token works for every account your Drip user can open.

## Connect Drip to Plandalf

1.  [Find Drip in the Marketplace](#find-drip-in-marketplace)

    In Plandalf, open **Automation** in the sidebar and choose the **Marketplace** tab. Find **Drip** under **Available now** and click **Connect**.

2.  [Paste the token and account ID](#paste-drip-credentials)

    In the **Connect Drip** window, keep or change the **Integration name**, paste your token into **API Token** and your account number into **Account ID**, then click **Connect**.

3.  [Check the result](#check-drip-connection)

    Plandalf checks both with Drip straight away by loading the account. When you see **Drip connected**, choose **Build an automation** to start a sequence, or **Not now**.

Your connection now appears under **Automation → My apps**. You can connect more than one Drip account; each step asks which account to use.

## Steps you can add

Every step below takes the subscriber’s email address. In a purchase sequence, insert `{{trigger.customer_email}}` from the variable menu.

The steps that add something (a subscriber, a tag, an event) create the subscriber first if Drip doesn’t have them yet, so you don’t need a separate create step. Remove Tag skips cleanly when the email isn’t in Drip.

### Create or Update Subscriber

Adds a subscriber to Drip, or updates the one with that email.

-   **Email Address** (required).
-   **First Name**, usually `{{trigger.customer_first_name}}`.
-   **Last Name**, usually `{{trigger.customer_last_name}}`.
-   **Custom Fields**: pairs of a Drip custom field identifier and a value, for example `plan` and `{{trigger.line_items_summary}}`. Use the identifier as Drip shows it under **Subscribers → Custom Fields**. Blank values are skipped, so an empty variable never wipes data in Drip.

### Apply Tag

Applies one or more tags to a subscriber, creating the subscriber and any new tags as needed. Tags are added to the ones the subscriber already has.

-   **Email Address** (required).
-   **Tags** (required): pick tags from your Drip account, or type a name to create a new tag. Typed names can include variables from the trigger or earlier steps.
-   **First Name**, used if the subscriber is new to Drip.

### Remove Tag

Removes a tag, for example when someone is refunded. If the email isn’t in Drip, the step is skipped rather than failed.

-   **Email Address** (required).
-   **Tag** (required): a tag from your Drip account.

### Record Event

Records a custom event on the subscriber. In Drip, start a workflow or rule from a custom event with the same name to send the right emails after a purchase.

-   **Email Address** (required).
-   **Event Name** (required): the event as Drip will show it, for example “Bought Retain Live ticket”. Drip matches workflow triggers on this exact name, so keep it the same in both places.
-   **Event Properties**: extra details for the event, as name and value pairs, for example `product` and `{{trigger.line_items_summary}}`. Add `value` set to `{{trigger.total}}` to count the event as revenue in Drip. `{{trigger.total}}` is already in cents, which is what Drip expects. Blank values are skipped.
-   **Occurred At**: when it happened, for example `{{trigger.paid_at}}`. Leave it blank to use the time the step runs.
-   **First Name**, used if the subscriber is new to Drip.

> [!NOTE]
> **Purchases are sent as events, not Drip orders**
> Record Event sends a purchase to Drip as a custom event on the subscriber. Plandalf doesn’t send orders to Drip’s ecommerce order API, so purchases don’t appear as Drip orders or products. Use the event name, its properties and tags to segment buyers instead.

## Start a sequence from Drip

Choose **Drip** as the trigger app to start a Plandalf sequence from something that happens in Drip:

-   **Subscriber Created**: a new subscriber is added to your Drip account.
-   **Tag Applied to Subscriber**: a tag is applied. Pick a **Tag** to fire only for that tag, or leave it blank for any tag.
-   **Subscriber Unsubscribed**: a subscriber unsubscribes from all your Drip emails.

You don’t need to set up anything in Drip. When you save the trigger, Plandalf adds a webhook to your Drip account, which you can see under **Settings → Webhooks**, and the trigger’s **2\. Config** tab shows **Connected to Drip**. Deleting the trigger removes the webhook again.

Each trigger gives later steps the subscriber’s `email`, `first_name`, `last_name`, `subscriber_id`, `status`, `custom_fields` and `tags`, plus the `tag` on Tag Applied to Subscriber. A common use is the [Enroll in Promo step](https://plandalf.com/docs/product-guides/integrations/plandalf#steps-plandalf-can-run), which starts a promo timer for anyone Drip tags as a lead.

Drip has many more webhook events, such as email opens and clicks. Plandalf doesn’t have triggers for those.

## Example: tag ticket buyers and start their emails

This sequence tags everyone who buys an event ticket and records the purchase, so a Drip workflow can send the ticket emails.

1.  [Create the sequence](#drip-example-create)

    Go to **Automation → My Sequences**, create a sequence and name it, for example “Ticket buyers to Drip”.

2.  [Set the trigger](#drip-example-trigger)

    Choose **Plandalf** as the app and **Checkout Completed** as the trigger event. Under **Offer**, pick the ticket checkout. On **3\. Test**, pick a recent checkout as the sample record so the variable menu fills with real values.

3.  [Tag the buyer](#drip-example-tag)

    Click **Add a step**, choose **Drip** and **Apply Tag**, and pick your Drip account. Set **Email Address** to `{{trigger.customer_email}}`, add a tag such as “Retain Live 2027” to **Tags**, and set **First Name** to `{{trigger.customer_first_name}}`.

4.  [Record the purchase](#drip-example-event)

    Add a second step: **Drip**, **Record Event**. Use the same email, set **Event Name** to “Bought Retain Live ticket”, and add two **Event Properties**: `product` set to `{{trigger.line_items_summary}}` and `value` set to `{{trigger.total}}`.

5.  [Start the Drip workflow](#drip-example-workflow)

    In Drip, create a workflow that starts when a subscriber performs the custom event “Bought Retain Live ticket”, and add your ticket emails to it.

6.  [Test and turn it on](#drip-example-test)

    Run each step’s test. Testing makes a real change in Drip, so use your own email or a test subscriber. Then turn the sequence **On**.

Test purchases skip automations by default. To try the whole flow with a test card, open the sequence’s **Settings**, switch on **Run on test purchases**, buy through the checkout’s test link, and switch it off again when you’re done.

## Remove the tag on refund

Take the tag back from refunded buyers with the [Remove access on refund](https://plandalf.com/docs/product-guides/integrations/plandalf#remove-access-on-refund) template.

1.  [Add the template](#drip-refund-add)

    Go to **Automation → Templates**, find **Remove access on refund** and click **\+ Add**. Pick the same checkout as your purchase sequence. Plandalf creates the sequence and opens it.

2.  [Pick the tag](#drip-refund-tag)

    Open the **Remove Tag** step. **Email Address** is already set to `{{trigger.customer_email}}`. Pick the tag your purchase sequence applies, such as “Retain Live 2027”. To remove more than one tag, add another **Remove Tag** step for each.

3.  [Turn it on](#drip-refund-on)

    The trigger is **Invoice Refunded** with **Full refunds only** on, so a partial refund leaves the tag alone. Turn the sequence **On**.

The template adds a removal step for every connected app that has one, so you may see steps for other apps in the same sequence. Set them up too, or delete the ones you don’t need.

## Common errors

| What you see | What to do |
| --- | --- |
| **Authentication failed** when connecting | Drip’s reason is shown with it. Check the **API Token** is the one from **Settings → User Settings**, that the **Account ID** is the number only, and that your Drip user can open that account. Plandalf keeps the failed connection in **My apps**. Open it there, fix the details and choose **Test Connection**, rather than connecting again. |
| Steps fail after you generated a new Drip token | The old token stopped working. Open the connection in **My apps**, paste the new token and choose **Test Connection**. |
| “Email is empty” | The email field didn’t resolve. Map it to `{{trigger.customer_email}}` or another step’s email output, and check the trigger sample has an email. |
| “… is not a valid email address” | The email field resolved to something that isn’t an email. Check which variable it uses. |
| “At least one tag is required” | **Tags** on **Apply Tag** is empty, or every entry resolved to blank. Pick or type a tag. |
| “Pick the Drip tag to remove” | The **Tag** on **Remove Tag** is empty. Pick a tag. |
| “Event name is empty” | **Event Name** on **Record Event** is blank. Type the name your Drip workflow starts on. |
| “… is not a date Drip can read” | **Occurred At** isn’t a date. Use a date variable such as `{{trigger.paid_at}}`, or leave it blank. |
| Remove Tag shows **skipped** | Drip has no subscriber with that email. Nothing needed changing. |
| “Drip didn’t accept the webhook” on a Drip trigger | Drip’s reason is shown underneath. Fix it, usually a new token or a removed connection, then click **Try again**. |
| A step fails with a rate limit message | Drip allows 3,600 requests an hour per account, and refuses two changes to the same subscriber at the same moment. Plandalf retries twice automatically. If it still fails, re-run the step once the burst has passed. |

## Related guides

-   [Automations overview](https://plandalf.com/docs/product-guides/integrations/plandalf)
-   [Create a checkout](https://plandalf.com/docs/product-guides/checkouts/create)
-   [Plandalf with Drip](site:/platforms/drip)

Source: https://plandalf.com/docs/product-guides/integrations/drip