ActionDripUpdated September 2026
How do I apply a Drip tag to a subscriber?
Short answer: You can apply tag in Drip by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Drip Apply Tag action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 | The email address. Used as the recipient or identifier depending on context. |
Tag tag | string | Required | – |
Sample request
{"email": "e.g. user@example.com","tag": "{{trigger.tag}}"}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Apply Tag.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Apply Tag.
What does the Apply Tag action do in Drip?
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.
What inputs does Apply Tag require?
Required: Subscriber Email, Tag. 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 Apply Tag support batch operations?
Run Apply Tag 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
Other Drip actions.
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.
ActionFind Subscriber by Email
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.
ActionRecord 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.
ActionRemove Drip Tag
Removes a specific tag from a subscriber. For "campaign ended" or "qualification expired" state-exit transitions.
ActionTag 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.
ActionTrack Drip Event
Logs a custom event for a subscriber with optional properties. Drives event-based campaign triggers in Drip's automation engine.