Tag Drip Subscriber: Drip action

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
Subscriber Email email	string	Required	Subscriber Email. e.g. "user@example.com"
Tag Name tag	string	Required	Tag Name. Example: customer

Sample request

{
  "email": "user@example.com",
  "tag": "e.g. customer"
}

Returns

{
  "success": true
}

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

FAQ

Questions about Tag Drip Subscriber.

What does the Tag Drip Subscriber action do in Drip?

Alias for Apply Tag — adds a tag to a subscriber by email. For Drip's automation hooks where tag application is the trigger.

What inputs does Tag Drip Subscriber require?

Required: Subscriber Email, Tag Name. 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 Tag Drip Subscriber support batch operations?

Yes. Run Tag Drip Subscriber 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