Track Iterable Event: Iterable 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
Email email	string	Required	The email address. Used as the recipient or identifier depending on context.
Event Name eventName	string	Required	—
Timestamp (UNIX seconds) createdAt	string	Optional	—
Data Fields (JSON) dataFields	string	Optional	—

Sample request

{
  "email": "e.g. user@example.com",
  "eventName": "{{trigger.eventName}}",
  "createdAt": "{{trigger.createdAt}}",
  "dataFields": "{{trigger.dataFields}}"
}

Returns

{
  "msg": "Success",
  "code": "Success"
}

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

FAQ

Questions about Track Iterable Event.

What does the Track Iterable Event action do in Iterable?

Pushes a custom behavioural event with optional properties. Drives Iterable workflow triggers. For "server-side action happened → start the matching journey" patterns.

What inputs does Track Iterable Event require?

Required: Email, 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 Iterable 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 Iterable Event support batch operations?

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

More actions