ActionDripUpdated September 2026

How do I record a custom event in Drip?

Short answer: You can record custom event in Drip by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Drip Record Custom Event action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Record Custom Event in Drip — start free All 7 Drip actions

Record Custom Event in Drip — start free

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.

Triggered by

Apps that pair well as the trigger for Record Custom Event.

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

Run Record Custom Event 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