Track Custom Event: Customer.io 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
Customer Identifier identifier	string	Required	Customer Identifier. e.g. "user@example.com"
Event Name name	string	Required	Event Name. Example: purchase_completed
Event Data (JSON) data	string	Optional	Custom data attached to the event

Sample request

{
  "identifier": "user@example.com",
  "name": "e.g. purchase_completed",
  "data": "{\"product\": \"Pro Plan\", \"amount\": 99}"
}

Returns

{
  "success": true
}

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

FAQ

Questions about Track Custom Event.

What does the Track Custom Event action do in Customer.io?

Pushes a behavioural event into Customer.io's event store. Journeys and campaigns can trigger on these. The standard hook for "server-side action happened → fire CIO event to start the matching journey".

What inputs does Track Custom Event require?

Required: Customer Identifier, Event Name. 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 Customer.io 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 Custom Event support batch operations?

Yes. Run Track Custom Event inside a Loop node to process arrays. Tiny Command handles Customer.io's rate limits automatically so you don't have to throttle manually.

More actions