- Integrations
- /
- Drip
- /
- Actions
- /
- Record Custom Event
ActionDripUpdated May 2026
How do I record a custom event in Drip?
Short answer: Drop the "Drip → Record Custom Event" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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
Other Drip actions.
Action
Apply Tag
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.
ActionCreate 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.
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.
Send record custom event from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.