ActionDripUpdated September 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.

Field	Type	Required	Description
Email or Subscriber ID id_or_email	string	Required	The 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.

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 run history shows the failed step with its input and the error message Drip returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Find Subscriber by Email support batch operations?

Run Find Subscriber by Email inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Drip's rate limits.

More actions