Start free
ActionDripUpdated June 2026

How do I look up a Drip subscriber?

Short answer: You can find subscriber by email in Drip by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Drip Find Subscriber by Email action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Find Subscriber by Email in Drip — start free All 7 Drip actions
Find Subscriber by Email in Drip — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Email or Subscriber ID
id_or_email
stringRequiredThe email address. Used as the recipient or identifier depending on context.
Sample request
{
  "id_or_email": "e.g. user@example.com"
}
Returns
{
  "subscribers": [
    {
      "id": "abc",
      "email": "jane@x.com",
      "status": "active",
      "first_name": "Jane"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Find Subscriber by Email.

Any of these apps can fire this action as part of a workflow.

Gmail → Drip
1 Gmail triggers
Slack → Drip
13 Slack triggers
Google Sheets → Drip
2 Google Sheets triggers
HubSpot → Drip
18 HubSpot triggers
FAQ

Questions about Find Subscriber by Email.

What does the Find Subscriber by Email action do in Drip?
Returns a subscriber by exact email match. The standard "find before update" pattern; returns 404 if no match, which workflows can branch on to decide create vs update.
What inputs does Find Subscriber by Email require?
Required: Email or Subscriber ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Drip returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Find Subscriber by Email support batch operations?
Yes. Run Find Subscriber by Email inside a Loop node to process arrays. TinyCommand handles Drip's rate limits automatically so you don't have to throttle manually.
More actions

Other Drip actions.

Action
Apply Tag
Adds a tag to a Drip subscriber. Tags drive Drip's automation triggers and segmentation — apply a tag to fire the matching workflow downstream in Drip itself.
Action
Create Drip Subscriber
Creates or upserts a subscriber by email with custom fields, tags, and starting campaign. The base hook for "form submission → push to Drip" sync workflows in e-commerce email programs.
Action
Record Custom Event
Pushes a behavioural event tied to a subscriber. Drip campaigns can trigger on events for purchase-completion flows, abandoned-cart automations, post-trial conversions.
Action
Remove Drip Tag
Removes a specific tag from a subscriber. For "campaign ended" or "qualification expired" state-exit transitions.
Action
Tag Drip Subscriber
Alias for Apply Tag — adds a tag to a subscriber by email. For Drip's automation hooks where tag application is the trigger.
Action
Track Drip Event
Logs a custom event for a subscriber with optional properties. Drives event-based campaign triggers in Drip's automation engine.
Find Subscriber by Email in Drip — start free