Resources · Make integration

Drip Make integrationAutomate Drip with Make.

Can Make keep Drip in step with your shop, your billing tool and your CRM? The Drip Make integration gives you 40 modules: 3 triggers, 23 actions and 14 searches. This guide is for marketers who know Drip well and are new to Make, and it walks you from the connection to a working first scenario.

Try the Drip integration on MakeSee the 40 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Drip Make integration let you automate?

The Drip Make integration links your Drip account to Make, a visual tool where you chain apps together without code. The automation you build is called a scenario, and each brick in it is a module: Drip can start the scenario, or receive the orders, tags and subscribers that other tools send it.

Buyers who land in the right sequence. When your payment tool records a sale, Create/Update a Subscriber adds the buyer to Drip, then Start Someone on a Workflow drops them into your onboarding flow. Nobody exports a CSV of customers again.

Order history that Drip can segment on. A store that does not talk to Drip directly can still push each purchase through Create/Update an Order, so your post-purchase emails know what people bought. Record an Event covers the actions that are not orders, like a webinar attended.

Reporting outside Drip. Searches such as List Campaigns, List Broadcasts or List Conversions feed a spreadsheet or a dashboard your sales team already reads.

Know the limits before you start: the Drip documentation on Make lists no quota of its own, and flags that its content is AI-generated and worth checking with Drip. Anything the 40 modules do not cover goes through Make an API Call. If you want a structured path through the editor, the Make training starts from zero. Drip often has an n8n node as well; the n8n vs Make comparison lays out the criteria. When a scenario fails, the Make troubleshooting guide helps you read the error.

Connect

How do you connect your Drip account to Make?

  1. 01

    Add a Drip module

    In your Make account, open a scenario, add any Drip module and click Create a connection. A connection is your Drip account linked to Make once; every Drip module in every scenario then reuses it.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name like "Drip main store" helps as soon as you run more than one Drip account. You will pick it from a dropdown in later modules.

  3. 03

    Enter your Drip credentials

    You need an active Drip account and either an API Key (private integration) or an OAuth token (public integration). Paste what you copied from Drip, or follow the on-screen instructions, and Make saves the connection.

First scenario

Your first scenario: turn a new buyer into a Drip subscriber on a workflow

GoalWhen a sale lands in your payment tool, Make adds the buyer to Drip and starts them on your onboarding workflow.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Pick the trigger of the tool where your sales are recorded, for example your billing or payment app.

  2. 02

    Add Create/Update a Subscriber

    Click the + on the right of the trigger, search for Drip and choose Create/Update a Subscriber. Select your connection, then map the buyer's email from the first module.

  3. 03

    Chain Start Someone on a Workflow

    Add a second Drip module, Start Someone on a Workflow. Make lists the workflows it can read in your account: pick the onboarding one and map the same email.

  4. 04

    Test with Run once

    Click Run once and trigger a test sale. Each module shows the bundles it received, a bundle being one item passing through, here one buyer. Check the subscriber in Drip.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; keep that or change it, then switch the scenario on. Each module run counts as one operation on your plan.

Triggers

Which Drip triggers can start a scenario?

3 modules start a scenario when something happens in Drip. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Drip as soon as it happens.

Drip1Watch Events

Watch Events

Instant trigger

In Make“Triggers when there is a new event to process.”

Watch Events hands your scenario each new event Drip has to process, the moment Drip sends it, so the data can move to another tool without waiting for a schedule.

How it fires
instant, Drip calls Make through a webhook as soon as the event happens; the module carries the lightning badge.
When to use it
a lead does something in Drip that your sales team should hear about right away, in their CRM or chat.
Watch out
setup asks you to click Create a webhook before the connection, and the scenario must be switched on to receive anything.
Drip2Watch Subscribers

Watch Subscribers

Scheduled trigger

In Make“Triggers when a new subscriber is added.”

This trigger picks up every subscriber newly added to your Drip account and passes each one to the next module as its own bundle, ready to copy into a CRM or a sheet.

How it fires
scheduled, Make checks Drip on the scenario's schedule, every 15 minutes by default; the module shows the clock badge.
When to use it
you want new list sign-ups to appear in the tool your sales reps work from, without anyone exporting them.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, so a new subscriber can wait that long before the scenario sees them.
Drip3Watch Subscribers in the Campaign

Watch Subscribers in the Campaign

Scheduled trigger

In Make“Triggers when a new email is subscribed to the campaign.”

Narrower than Watch Subscribers, this one reacts only to emails newly subscribed to the campaign you choose, which keeps your scenario focused on one funnel.

How it fires
scheduled, Make checks Drip on the scenario's schedule and brings back the new subscriptions it finds since the last check.
When to use it
a lead-magnet campaign whose sign-ups should get a follow-up task, a tag in another tool or a row in a tracking sheet.
Watch out
it only reports new subscriptions; people who joined the campaign earlier never show up, so pull them once with List Everyone Subscribed to a Campaign.
Modules

What can Make do in Drip?

Drip gives you 37 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Drip1

Activate a Campaign

Action

In Make“Activates a selected campaign.”

Turn a paused Drip campaign back on from a scenario, so a sequence restarts because something happened elsewhere and not because someone remembered to log in.

When to use it
a product is back in stock in your store and the campaign that promotes it should resume.
Watch out
pair it with Pause a Campaign in a mirror scenario, otherwise the campaign only ever goes one way.
Drip2

Activate a Workflow

Action

In Make“Activates a selected workflow.”

Switches a Drip workflow on. That matters more than it looks, because Drip refuses to add anyone to a workflow that is not active.

When to use it
place it just before Start Someone on a Workflow when your team builds seasonal workflows and leaves them off until launch.
Watch out
switching it on enrolls nobody by itself; Start Someone on a Workflow still does that part.
Drip3

Create/Update an Order

Action

In Make“Creates or updates an order. If you receive errors please check required parameters in the documentation properly. A provider and an order ID are required. Either a person ID or an email must be included.”

Sends a purchase to Drip so your segments and post-purchase emails know what each customer bought, even when your store has no native Drip link.

When to use it
an order is confirmed in your checkout or invoicing tool and Drip should know about it.
Watch out
a provider and an order ID are required, plus either a person ID or an email; missing one of them is the usual cause of errors.
Drip4

Create/Update a Subscriber

Action

In Make“Creates or updates a subscriber.”

The workhorse of most Drip scenarios: it adds a person to Drip, or updates them if they are already there, so one module covers both cases.

When to use it
any time a contact form, a webinar tool or a payment app produces a new person you want in your lists.
Watch out
if you only ever change existing people, Update a Subscriber states that intent more clearly.
Drip5

Delete a Subscriber

Action

In Make“Deletes a subscriber.”

Removes a subscriber from your Drip account entirely, which is what you need when someone asks for their data to be erased.

When to use it
a deletion request arrives through your support desk or privacy form, and the person must disappear from Drip too.
Watch out
a deletion cannot be undone from Make. If the goal is only to stop emails, Unsubscribe from All Mailings keeps them in Drip.
Drip6

Fetch a Campaign

Action

In Make“Fetches a campaign linked to an account.”

Pulls the details of one campaign linked to your account, so a later module can reuse its details instead of you typing them.

When to use it
a scenario posts a message to your team chat about a campaign and needs its current information in the text.
Watch out
you need to know which campaign you want; to browse them all, start with List Campaigns.
Drip7

Fetch a Form

Action

In Make“Fetches a form.”

Retrieves a single Drip form, handy when a scenario must know which form a sign-up came through and label it properly downstream.

When to use it
you send new leads to a CRM and want the form's name stored with each contact as the lead source.
Watch out
it reads one form you point to; List Forms is the module that shows you every form in the account.
Drip8

Fetch an Account

Action

In Make“Fetches an account.”

Returns the details of one Drip account, which helps anyone running several accounts confirm which one a scenario is acting on.

When to use it
a shared scenario writes to a reporting sheet and each row should carry the name of the account it came from.
Watch out
the connection decides what you can read, so the account must be reachable with the credentials you entered.
Drip9

Fetch a Subscriber

Action

In Make“Fetches a subscriber.”

Looks up one person in Drip and brings back their record, so the next module can decide what to do based on what Drip already knows.

When to use it
a support ticket comes in and you want the customer's Drip profile attached before an agent replies.
Watch out
if the person does not exist, the module has nothing to return; plan a filter or a fallback route after it.
Drip10

Fetch a User

Action

In Make“Fetches an authenticated user.”

Tells you which Drip user the connection is authenticated as. It is a small module, but it removes doubt when several people share scenarios.

When to use it
checking that a scenario inherited from a colleague still runs under the right Drip login before you change anything.
Watch out
it describes the connected user, not your subscribers; for people on your lists, use Fetch a Subscriber.
Drip11

Fetch a Workflow

Action

In Make“Fetches a workflow.”

Brings back one Drip workflow with its details, so your scenario can check it before sending anyone into it.

When to use it
right before Start Someone on a Workflow, to check the workflow you target, since Drip adds nobody to one that is not active.
Watch out
fetching changes nothing in Drip; it only reads, so pair it with a filter to act on what it finds.
Drip12

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Your escape hatch when none of the 40 modules does exactly what you need: it calls any endpoint of the Drip API with the connection you already set up.

When to use it
a Drip feature exists in the API but has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Drip API reference open and test with Run once before switching the scenario on.
Drip13

Pause a Campaign

Action

In Make“Pauses a selected campaign.”

Stops a Drip campaign from sending, triggered by an event outside Drip rather than a manual click in the dashboard.

When to use it
a promotion sells out in your store and the emails promoting it should stop before more people click through to an empty page.
Watch out
the campaign stays paused until something turns it back on; Activate a Campaign is the matching move.
Drip14

Pause a Workflow

Action

In Make“Pauses a selected workflow.”

Freezes a Drip workflow. It is the brake you want at hand when a workflow sends the wrong message or relies on data that just broke.

When to use it
your store reports a pricing error and the post-purchase workflow quoting that price should hold until it is fixed.
Watch out
while paused, Start Someone on a Workflow will not add anyone to it.
Drip15

Record an Event

Action

In Make“Pushes an event to the Drip. Note: you can configure actions to be fired in the Drip on the event.”

Pushes a custom event into Drip, such as a demo booked or a course lesson finished, so Drip can react to behavior that happens in other tools.

When to use it
your webinar platform marks someone as attended and Drip should send the replay only to them.
Watch out
the event alone sends nothing; set up in Drip the actions that fire on it.
Drip16

Remove a Subscriber from Campaigns

Action

In Make“Removes a subscriber from one or all campaigns.”

Takes a person out of one campaign, or out of all of them, while keeping them in your Drip account.

When to use it
a lead signs a contract in your CRM and should stop receiving the nurture campaign meant for prospects.
Watch out
choosing all campaigns is broad; if you only mean to exit one funnel, select that campaign so other sequences keep running.
Drip17

Remove a Subscriber Tag

Action

In Make“Removes a subscriber tag.”

Strips one tag from a subscriber, which is often how you move someone out of a Drip segment without touching anything else on their profile.

When to use it
an unpaid invoice gets settled and the "payment-overdue" tag has to go so reminders stop.
Watch out
the tag must match the one in Drip exactly; List Tags shows you the spelling your account uses.
Drip18

Remove Someone from a Workflow

Action

In Make“Removes a subscriber from a workflow.”

Pulls a subscriber out of a Drip workflow before its end, so an email sequence does not keep talking to someone whose situation changed.

When to use it
a trial user upgrades in your app and the trial-conversion workflow should stop for them.
Watch out
it only affects the workflow you pick; campaigns the person is on need Remove a Subscriber from Campaigns.
Drip19

Start Someone on a Workflow

Action

In Make“Adds a subscriber to a workflow. Note: If the workflow is not active, the subscriber will not be added to the workflow.”

Drops a subscriber into a Drip workflow, which lets an event in any other app kick off an automated sequence in Drip.

When to use it
a buyer pays in your checkout tool and must enter the onboarding workflow straight after Create/Update a Subscriber.
Watch out
if the workflow is not active, Drip does not add the person; check it with Fetch a Workflow or turn it on with Activate a Workflow first.
Drip20

Subscribe Someone to a Campaign

Action

In Make“Subscribes a given email to a campaign.”

Signs a given email up to a Drip campaign from a scenario, without the person filling in a Drip form themselves.

When to use it
someone downloads a guide from a landing page built in another tool and the matching email course should start.
Watch out
campaigns and workflows are different objects in Drip; for a workflow, use Start Someone on a Workflow.
Drip21

Tag a Subscriber

Action

In Make“Tags a subscriber.”

Adds a tag to a subscriber, the simplest way to feed Drip segments with information that lives in other tools.

When to use it
a customer opens a support ticket about a product line and you tag them so upsell emails for it pause.
Watch out
the name must match the tag your segments rely on; copy it exactly from List Tags.
Drip22

Unsubscribe from All Mailings

Action

In Make“Unsubscribes a subscriber from all mailings.”

Stops every email to one subscriber while keeping them in your Drip account, which is the clean answer to an opt-out received elsewhere.

When to use it
a customer asks your support team to stop all marketing email and you want Drip to reflect it without a manual step.
Watch out
this is broader than leaving a single campaign; for that, use Remove a Subscriber from Campaigns.
Drip23

Update a Subscriber

Action

In Make“Updates a subscriber.”

Changes the details of a subscriber who already exists in Drip, so the profile follows what your CRM or store knows about them.

When to use it
a customer edits their name or company in your app and Drip should personalize emails with the new version.
Watch out
it expects an existing person; when you are not sure they exist, Create/Update a Subscriber covers both cases.
Drip24

List Accounts

Search

In Make“Retrieves a list of all accounts.”

Returns every Drip account your connection can reach, one bundle per account, which is the starting point for multi-account reporting.

When to use it
an agency loops over each client account to collect figures into one shared sheet.
Watch out
each account becomes its own bundle, and every module after it runs once per account, which multiplies operations.
Drip25

List Broadcasts

Search

In Make“Retrieves a list of all broadcasts.”

Gathers the broadcasts of your Drip account so you can review them outside Drip next to the rest of your marketing data.

When to use it
building a content calendar in a spreadsheet that shows what each broadcast was and when it went out.
Watch out
a search can return zero, one or many bundles; add an aggregator if you want a single summary instead of one row per broadcast.
Drip26

List Campaigns

Search

In Make“Retrieves a list of campaigns linked to an account.”

Retrieves the campaigns tied to a Drip account, which gives your scenario a menu to pick from instead of a hardcoded campaign.

When to use it
a reporting scenario writes every campaign into a dashboard your manager checks.
Watch out
the module brings back the campaigns, not their subscribers; for those, use List Everyone Subscribed to a Campaign.
Drip27

List Campaign Subscriptions

Search

In Make“Retrieves a list of all campaign subscriptions.”

Shows which campaigns people are subscribed to, seen from the subscription side rather than from one campaign.

When to use it
auditing a subscriber who complains about too many emails, to see every campaign they are enrolled in before you clean up.
Watch out
expect several bundles back; filter them before acting, or a removal module will run on each one.
Drip28

List Conversions

Search

In Make“Retrieves a list of all conversions.”

Pulls every conversion recorded in your Drip account, so that data can live next to your sales numbers.

When to use it
feeding a revenue dashboard where marketing and sales look at the same figures without logging into Drip.
Watch out
the module only reads what Drip holds; nothing in the list changes, and several bundles come back, so aggregate them for one dashboard line.
Drip29

List Custom Fields

Search

In Make“Retrieves a list of all custom fields.”

Reveals the custom fields your Drip account uses, a quick way to know what data you can map before writing a subscriber.

When to use it
preparing a scenario that syncs CRM properties to Drip, when you need the exact field names on the Drip side.
Watch out
run it with Run once while you build, then remove it; keeping it in a live scenario spends operations for nothing.
Drip30

List Events in an Account

Search

In Make“Retrieves a list of all events linked to an account.”

Brings back the events recorded in a Drip account, so you can check which actions Drip already knows about before inventing new ones.

When to use it
before adding Record an Event to a scenario, to reuse an existing event name and keep your Drip rules consistent.
Watch out
it is a snapshot you call on demand; to react as events happen, Watch Events is the right module.
Drip31

List Everyone Subscribed to a Campaign

Search

In Make“Retrieves a list of everyone subscribed to a selected campaign.”

Returns every person subscribed to the campaign you select, one bundle each, ready to be copied, tagged or counted.

When to use it
a campaign ends and its audience should move into a CRM list for a sales follow-up.
Watch out
on a large campaign, each person becomes one bundle and every later module runs once per person, so watch your operations.
Drip32

List Forms

Search

In Make“Retrieves a list of all forms linked to an account.”

Lists the forms linked to your Drip account, which helps you map sign-up sources without opening Drip.

When to use it
documenting which form feeds which list, or preparing a report that groups new subscribers by form.
Watch out
it lists forms, not their submissions; new people arriving through a form show up with Watch Subscribers.
Drip33

List Subscribers

Search

In Make“Retrieves a list of all subscribers.”

Retrieves the subscribers in your Drip account, the base for a one-off sync or a cleanup across tools.

When to use it
moving to a new CRM and wanting every Drip contact copied over before the switch.
Watch out
this can produce a lot of bundles and operations; for new people only, Watch Subscribers does the job with less volume.
Drip34

List Tags

Search

In Make“Retrieves a list of all tags used in an account.”

Shows every tag used in your Drip account, so the tags you add or remove from Make match the ones Drip already relies on.

When to use it
building a tag sync with your CRM, when both sides need the same spelling to line up.
Watch out
useful while you set things up; in a live scenario, one call per run is plenty.
Drip35

List Webhooks

Search

In Make“Retrieves a list of all webhooks.”

Lists the webhooks registered in your Drip account, which helps when you want to see what is listening to Drip events.

When to use it
Watch Events stopped receiving anything and you want to check that a webhook is still in place.
Watch out
it only reads; the webhook for Watch Events is created from Make with Create a webhook.
Drip36

List Workflows

Search

In Make“Retrieves a list of all workflows.”

Brings back your Drip workflows, so a scenario can look at them all rather than one you picked by hand.

When to use it
a review that sends your marketing lead the full list of workflows in one message.
Watch out
one bundle per workflow; to act on a single one, add a filter before Activate a Workflow or Pause a Workflow.
Drip37

List Workflow Triggers

Search

In Make“Retrieves a list of all workflow triggers.”

Reveals the triggers set on your Drip workflows, the rules inside Drip that decide who enters them, gathered in one list.

When to use it
auditing why some subscribers enter a workflow twice, once from Drip and once from your Make scenario.
Watch out
these are Drip's own triggers, distinct from the Make triggers of this page such as Watch Subscribers.
Need help

Need help automating Drip with Make?

A person reads every message.

FAQ

Drip and Make: common questions

01Is the Drip Make integration free?
Yes, on the Make side. Drip is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in credits per month. You still need an active Drip account, which Drip bills on its own terms.
02What do you need to connect Drip to Make?
An active Drip account and one of two credentials: an API Key for a private integration or an OAuth token for a public one. In Make, add a Drip module, click Create a connection, name it if you like, then paste your credentials or follow the on-screen steps. For your own OAuth app, create it in the OAuth Applications section of Drip, use the callback URI given in the Make documentation, then copy the Client ID and Client secret.
03Does the Drip Make integration react in real time?
It depends on the trigger. Watch Events is instant: Drip calls Make through a webhook as soon as an event happens, so the scenario starts right away. Watch Subscribers and Watch Subscribers in the Campaign are scheduled: Make checks Drip on the scenario's schedule, every 15 minutes by default, and no faster than every 15 minutes on the Free plan. Paid plans can check every minute. Of the three Drip triggers, Watch Events is the only instant one.
04What if a Drip module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Drip API with the connection you already created, so a feature without a dedicated module is still within reach. You write the request yourself, so keep the Drip API reference open and test with Run once. The Make documentation for Drip lists no specific limit, but warns that its content is AI-generated; check important details with Drip before you build on them.
05Should you use Make or n8n for Drip?
It depends on the tool your team already works in. Make offers 40 Drip modules, a visual editor and a Free plan to test with. Drip often has an n8n node too, so check that the actions you need exist there before choosing. Compare the modules each side offers for your exact use case, rather than a general ranking. The n8n vs Make comparison linked earlier on this page lays out the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations