Track Drip Event: 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"
Event Action action	string	Required	Event Action. Example: Completed purchase
Properties (JSON) properties	string	Optional	Custom event properties

Sample request

{
  "email": "user@example.com",
  "action": "e.g. Completed purchase",
  "properties": "{\"product\": \"Pro Plan\", \"value\": 99}"
}

Returns

{
  "success": true
}

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

FAQ

Questions about Track Drip Event.

What does the Track Drip Event action do in Drip?

Logs a custom event for a subscriber with optional properties. Drives event-based campaign triggers in Drip's automation engine.

What inputs does Track Drip Event require?

Required: Subscriber Email, Event Action. 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 Track Drip Event support batch operations?

Yes. Run Track Drip Event 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