ActionDripUpdated May 2026

How do I look up a Drip subscriber?

Short answer: Drop the "Drip → Find Subscriber by Email" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 7 Drip actions

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 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. Tiny Command handles Drip's rate limits automatically so you don't have to throttle manually.

More actions