Connectors

/

Drip

/

Handle a Drip opt-out request
Write

Honour each Drip opt-out at exactly the scope asked

For email marketers and support staff who want opt-out requests handled precisely in Drip, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Handle a Drip opt-out request
Pat at pat@contoso.com wants out of the Weekly Tips series in Drip but still wants other emails.
Pat Morgan is active in Drip and in 3 email series. - Will change: removed from Weekly Tips only - Will not change: Product Updates and Events stay, and status stays active - Not done: no full unsubscribe Shall I remove Pat from Weekly Tips?
Drip
Sample figures. Your results come from your own account.
drip-get-subscriber
drip-get-campaign-subscriber
drip-get-workflow
drip-remove-subscriber-from-campaign
drip-remove-subscriber-from-all-campaigns
drip-remove-subscriber-from-workflow
drip-unsubscribe-subscriber

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Drip

Drip
Run it on your own Drip data.

Connect Drip, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

An opt out request handled too broadly cannot be undone

One person wants out of a single series, another wants no email at all. Acting in Drip by hand risks removing too little, or a full unsubscribe that cannot be reversed without consent.

Without PopdockAI

  • Find the subscriber in Drip
  • Work out which series they meant
  • Remove them from the right place
  • Risk unsubscribing them from everything

With PopdockAI

  • The scope is confirmed before anything is touched
  • Their series are listed and the named one matched
  • You see what will and will not change, then confirm
  • One change at the narrowest scope, read back after

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Act on an opt-out request from `{email}` at scope `{scope}`: a campaign name, all-campaigns, workflow followed by the workflow name, or unsubscribe (stop all mail). If `{scope}` is blank, ask which scope they want before writing anything.

**Step 1: Read the subscriber**

Call `drip-get-subscriber` with `email` = `{email}`. If no one matches, stop and say so. If already unsubscribed, report that and stop unless the request was a specific campaign.

**Step 2: Show what they currently get**

Call `drip-get-campaign-subscriber` with `email` = `{email}` and list their campaigns.

**Step 3: Resolve the target**

* Campaign name: match it against the list from Step 2. If it is not there, they are not in it; say so and stop. If several match, list them and stop.
* workflow: call `drip-get-workflow` with `name` (then `name.contains`) to get the workflow-id. If several match, list them and stop.

**Step 4: Confirm**

State exactly what will happen, and what will not (for example, removing from one campaign leaves their other campaigns and broadcasts running). Wait for the user to say yes.

**Step 5: Act, once**

* One campaign: `drip-remove-subscriber-from-campaign` with `id` = `{email}` and `campaign_id`.
* all-campaigns: `drip-remove-subscriber-from-all-campaigns` with `id` = `{email}`.
* workflow: `drip-remove-subscriber-from-workflow` with `id` = `{email}` and `workflow_id`.
* unsubscribe: `drip-unsubscribe-subscriber` with `id` = `{email}`.

**Step 6: Verify**

Re-read with `drip-get-subscriber` and `drip-get-campaign-subscriber` and report the result. Workflow removal cannot be read back; say the call succeeded.

**Rules & Guidelines:**

* Use the narrowest scope that satisfies the request. Never escalate to unsubscribe unless that was the scope asked for.
* Call exactly one remove or unsubscribe tool. Do not call `drip-update-subscriber`, `drip-add-subscriber` or any tag tool.

**Validation:**

* If the request is ambiguous between scopes, ask; an unwanted full unsubscribe cannot be undone without the person's consent.

Who it's for

One answer, three teams that use it

Support agents

Handle opt out requests correctly

Remove someone from exactly what they asked, with a read-back to confirm in your reply.

Remove sam@fabrikam.com from the Product Updates campaign in Drip only.

Email marketers

Keep subscribers who only want less email

Narrow removals keep people on the series they still want instead of losing them entirely.

Take jo@contoso.com out of the Onboarding workflow in Drip but keep their other emails.

Privacy officers

Process full unsubscribes with care

A full unsubscribe happens only when asked for and confirmed, with the result reported.

Fully unsubscribe lee@northwindtraders.com from all Drip email, they asked us to stop.

How it works

What PopdockAI does when you ask

You give the email and the scope, and your AI assistant checks the subscriber and their series. One change is made, at the narrowest scope, only after you confirm.

01

Ask

You give the email and the scope, from one campaign to a full unsubscribe.

Your AI tool

02

Check

It reads the subscriber, lists their email series and matches the one you named.

drip-get-subscriber
drip-get-campaign-subscriber
drip-get-workflow

03

Confirm

You see exactly what will and will not change.

No items found.

04

Act

It makes one change at the narrowest scope and reads the record back.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for Drip and one secure connection to your AI tool. No code, no exports.

get-data

drip-get-subscriber

Returns Drip people (subscribers) with name, email, location, tags, status, GDPR consent, lead score and lifetime value. Filter by exact email, email domain, tag, status, country, minimum lead score, minimum lifetime value or date added.
get-data

drip-get-campaign-subscriber

Returns the people subscribed to each Drip email series campaign, with the campaign's status and the person's tags and lead score. Filter by campaign id or name, a person's email, subscriber status or minimum lead score.
get-data

drip-get-workflow

Returns Drip automation workflows with their status and created date. Filter by name, status or created date range.
run-action

drip-remove-subscriber-from-campaign

Removes a Drip subscriber, identified by subscriber id or email, from one email series campaign.
run-action

drip-remove-subscriber-from-all-campaigns

Removes a Drip subscriber, identified by subscriber id or email, from every email series campaign they are in.
run-action

drip-remove-subscriber-from-workflow

Removes a Drip subscriber, identified by subscriber id or email, from one workflow.
run-action

drip-unsubscribe-subscriber

Unsubscribes a Drip subscriber, identified by subscriber id or email address, from all mailings.
Read only.Nothing in Drip Changes

This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.

How Popdock AI secures your data

The outcome

Every opt out honored at exactly the scope asked

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

One prompt template with infinite possibilities.

‍

Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation