Record Custom 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	The email address. Used as the recipient or identifier depending on context.
Event Action action	string	Required	Purchased product
Properties (JSON) properties	string	Optional	—

Sample request

{
  "email": "e.g. user@example.com",
  "action": "Purchased product",
  "properties": "{{trigger.properties}}"
}

Returns

{}

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

FAQ

Questions about Record Custom Event.

What does the Record Custom Event action do in Drip?

Pushes a behavioural event tied to a subscriber. Drip campaigns can trigger on events for purchase-completion flows, abandoned-cart automations, post-trial conversions.

What inputs does Record Custom 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 Record Custom Event support batch operations?

Yes. Run Record Custom 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