Drip Zapier integrationAutomate Drip with Zapier.
The Drip Zapier integration gives you 16 triggers and 7 actions, with no search step at all. Every trigger is instant, so a Drip Zap starts the moment a subscriber clicks, opens, bounces or gets tagged, even on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Drip Zapier integration actually does
The Drip Zapier integration links your Drip account to Zapier, a tool that runs automations for you. A Zap, the automation you build there, waits for something to happen in Drip (a tag, a click, an unsubscribe) and then acts on a subscriber: tag them, move them, record an event.
Three results come up again and again. First, a cleaner list: New Email Complained or New Email Bounced feeds Remove From Campaign or Add Tag to Subscriber, so people who flagged spam stop receiving mail. Second, sequences that hand over to each other: Complete Campaign followed by Subscribe to Campaign moves a reader from one series to the next. Third, behavior turned into labels: New Email Click, New Trigger Link Click or New Page Visit followed by Add Tag to Subscriber leaves a visible mark on the people who showed interest.
Here is what Zapier does not do for Drip. There is no search step, so a Zap cannot look up a subscriber first and decide afterwards. There is no ready-made action to delete a subscriber or edit a campaign. And nothing in the list sends an email directly: the actions change who is in which campaign, Drip does the sending. For the rest, API Request (Beta) reaches Drip with your connection, but it is a tool for someone comfortable with Drip's documentation.
The same app is covered on the Drip Make integration page, and n8n vs Zapier lays out how the platforms differ by criteria.
Zapier words you will see, in plain English
Eight terms cover everything on this page. Read them once, and the rest of the page will make sense.
- Zap
- The automation itself: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in Drip that starts the Zap, such as a new tag or an email click. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that tags, subscribes or removes a person in Drip for you.
- Task
- The unit Zapier bills: one action that completes successfully. Your plan's allowance is a count of those.
- Instant vs polling trigger
- Instant: the app tells Zapier as soon as the event happens. Polling: Zapier checks on a timer. All Drip triggers are instant.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
- Search step
- A step that looks up something that already exists in an app for the next steps to use. Drip offers none on Zapier.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it needs a paid plan.
What a Drip Zap costs in tasks
Drip is not a premium app, so it works on the free plan. The bill depends on actions, never on triggers.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks per month, two-step Zaps only
- Drip on ZapierNot a premium app
The trigger never costs a task, and neither does Zapier listening for new data. Each action that succeeds counts once, so a Zap with three actions uses three times what a one-action Zap uses, and a failed action is not counted. The free plan gives 100 tasks per month but only two-step Zaps: one trigger, one action. Add a filter, a second action or a search and the Zap becomes multi-step, which needs a paid plan. The interval grid below only concerns polling triggers; every Drip trigger is instant, so it does not apply here.
Connect your Drip account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Drip account linked to Zapier once, then reused by every Zap step that talks to Drip.
- 02
Pick Drip and confirm
Type Drip in the search box of the dialog, select it, then click Add connection. A new tab then opens on Drip's side, where the sign-in for that account happens.
- 03
Sign in and grant access
Log in with your Drip account and allow Zapier to access it. You need an account on Drip, plus access to any account you do not own yourself but want your Zaps to touch.
Your first Drip Zap, step by step
GoalWhen a subscriber flags one of your emails as spam, remove them from all their campaigns and tag them so the team can see why.
- 01
Build: choose the trigger
Create a Zap, pick Drip as the app and New Email Complained as the event. Select your connection, then choose the Drip account in the Account field.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items from your Drip account, so you can map from a real complaint rather than an invented one.
- 03
Add the first action
Add Drip with Remove From Campaign, choose the account and set it to remove the person from all campaigns. Map the subscriber's email from the trigger into Email Address.
- 04
Add the second action
Click the plus icon and add Add Tag to Subscriber with a tag such as "spam-complaint". Two actions make the Zap multi-step, which needs a paid plan.
- 05
Test each step
Run each step once and check in Drip that the test subscriber left the campaigns and now carries the tag, so a wrong mapping shows up before real subscribers go through it.
- 06
Publish
Click Publish to switch the Zap on. From then on, each spam complaint starts it right away and uses two tasks, one per successful action.
The 16 Drip triggers
16 events start a Zap when something happens in Drip, and 16 of them are instant: the app calls Zapier straight away, whatever your plan.
New Subscriber Tag
Instant triggerIn Zapier“Triggers when a tag is applied to a subscriber”
Starts your Zap the second a tag gets attached to a person in Drip. In practice, tags become remote controls: label someone in Drip and whatever follows in the Zap runs for that exact person, with their details ready to map into the next step.
New Email Bounced
Instant triggerIn Zapier“Triggers when an email to a subscriber bounces.”
Wakes up whenever an email Drip sent to a subscriber comes back undelivered. It turns a quiet deliverability problem into something your Zap can act on, one address at a time, instead of a number you only notice in a report weeks later.
New Email Click
Instant triggerIn Zapier“Triggers when a subscriber clicks an email.”
Fires as soon as a subscriber clicks inside one of your Drip emails. A click is the strongest signal an email can give you, and this trigger hands it to Zapier while the reader is probably still on your site.
New Trigger Link Click
Instant triggerIn Zapier“Triggers when a subscriber clicks a trigger link.”
Reacts only to clicks on the trigger links you set up in Drip, not to every link in the message. That precision is the whole point: one link equals one intent, so the Zap knows exactly which button the subscriber pressed.
New Email Complained
Instant triggerIn Zapier“Triggers when a subscriber issues a spam complaint about an email.”
Goes off when a subscriber marks one of your emails as spam. That is the one signal you cannot afford to ignore: a person who complains and keeps receiving mail hurts the reputation of every campaign you send afterwards.
Complete Campaign
Instant triggerIn Zapier“Triggers when a subscriber completes a campaign.”
Kicks in when a subscriber reaches the end of a Drip campaign. It is the natural handoff point between two sequences: the welcome series ends, and the Zap decides what comes next for that person.
New Subscriber
Instant triggerIn Zapier“Triggers when a new subscriber record is created.”
Triggers whenever a new subscriber record appears in Drip, however it got there. It is the broadest entry point of the integration, the moment a contact first exists in your list.
New Custom Event
Instant triggerIn Zapier“Triggers when a subscriber performs a custom event.”
Listens for the custom events that subscribers perform in Drip, the ones you named yourself, such as a trial started or a cart left behind. Whatever you track as an event becomes a starting point for a Zap.
New Email Open
Instant triggerIn Zapier“Triggers when a subscriber opens an email.”
Starts the Zap whenever a subscriber opens one of your Drip emails. Opens are a softer signal than clicks, yet they tell you who is still reading, which is useful when you want to separate an engaged audience from a dormant one.
Remove Subscriber Tag
Instant triggerIn Zapier“Triggers when a tag is removed from a subscriber.”
The mirror of New Subscriber Tag: it fires when a tag comes off a person in Drip. Removing a label is often how a status ends, so this is where you react to someone leaving a segment rather than joining it.
Remove Campaign Subscription
Instant triggerIn Zapier“Triggers when a subscriber is removed from a campaign.”
Fires when a subscriber is taken out of a Drip campaign. Note the wording: removed, not unsubscribed. It covers the cases where someone, or something, pulls the person out, rather than the person clicking the unsubscribe link.
New Campaign Subscription
Instant triggerIn Zapier“Triggers when a subscriber is added to a campaign.”
Triggers when someone is added to a Drip campaign. Where New Subscriber watches the list as a whole, this one watches campaign membership, so it tells you which sequence the person just entered.
New Global Unsubscribe
Instant triggerIn Zapier“Triggers when a subscriber unsubscribes from all mailings.”
This is the trigger for a subscriber opting out of all your mailings at once. This is the strongest exit a person can make, and the Zap learns about it immediately rather than at the next export.
New Campaign Unsubscribe
Instant triggerIn Zapier“Triggers when a subscriber unsubscribes from a campaign.”
Narrower than the global version: it fires when someone leaves one campaign only. The person is still on your list, just tired of that particular sequence, which leaves room for a softer next step.
Update Custom Field
Instant triggerIn Zapier“Triggers when a subscriber custom field is updated.”
A change to a custom field on a subscriber in Drip sets this one off. Custom fields often store the data that really matters to you (a plan, a city, a score), so a change there is frequently a change of situation.
New Page Visit
Instant triggerIn Zapier“Triggers when a subscriber visits a page that is bound to an automation rule trigger.”
Reacts when a known subscriber visits a page of your site, but only a page that is tied to a trigger in a Drip automation rule. It brings browsing behavior into Zapier without a separate tracking tool.
The 7 Drip actions
Drip gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Tag to Subscriber
ActionIn Zapier“Adds a tag to a subscriber.”
Attaches a tag to the subscriber whose email you provide. Tags are the lightest way to mark a person in Drip, and the New Subscriber Tag trigger reacts to them.
Trigger Event
ActionIn Zapier“Creates an event for a subscriber (e.g. "Signed up for a trial").”
Records a custom event on a subscriber, such as "Signed up for a trial". It shows up on the subscriber as something that happened, and it is exactly what the New Custom Event trigger listens for.
Remove Tag From Subscriber
ActionIn Zapier“Removes a tag from a subscriber.”
Takes a given tag off a subscriber. Use it to close a status as cleanly as you opened it, so segments based on that tag stay honest.
Subscribe to Campaign
ActionIn Zapier“Subscribes someone to a campaign.”
Puts a person into a specific Drip campaign. You choose the campaign, give the email, and can decide whether the double opt-in confirmation email goes out or follows the campaign's own setting.
Remove From Campaign
ActionIn Zapier“Unsubscribes someone from one (or all) of their campaigns.”
Unsubscribes someone from one of their campaigns, or from all of them. It is the brake pedal of the integration: the step that stops a sequence for a person who no longer belongs in it.
Create or Update Subscriber
ActionIn Zapier“Creates a new subscriber or update an existing one.”
Creates the subscriber in Drip, or updates them if the email address already exists. One action covers both cases, so you never need to know beforehand whether the person is already on your list.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
An advanced action that sends a raw request to Drip using the connection you already set up. It covers what the six ready-made actions do not, provided you know which Drip address to call.
When a Drip Zap breaks
Zapier links no help article to Drip, so the traps below come from how Zapier works in general and from the Drip actions themselves.
Most surprises with Drip come from one thing: triggers and actions talk about the same objects (tags, campaigns, events), which makes it easy to build a Zap that feeds itself. If a Zap misbehaves, the Zapier troubleshooting guide is the next stop.
The Zap triggers itself
New Subscriber Tag plus Add Tag to Subscriber on the same account, or New Custom Event plus Trigger Event, can fire over and over and burn through your tasks. Never wire them in a circle.Old subscribers are ignored
A Zap only reacts to what happens after you publish it. People tagged or subscribed before that will not run through it; moving the backlog is a separate job.A big import gets held back
Tag hundreds of people at once in Drip and Zapier's flood protection can hold the batch back instead of running every Zap at once.A removed subscriber is refused
With Reactivate if Removed switched off, Subscribe to Campaign gets a 422 error for anyone removed before, and the step stops there.
Need help automating Drip with Zapier?
A person reads every message.



