ActionIterableUpdated September 2026

How do I push a custom event to Iterable?

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

Track Iterable Event in Iterable — start free All 6 Iterable actions

Track Iterable Event in Iterable — 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
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.

Triggered by

Apps that pair well as the trigger for Track Iterable Event.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Iterable

2 Google Sheets triggers

HubSpot → Iterable

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Iterable 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 Track Iterable Event support batch operations?

Run Track Iterable 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 Iterable's rate limits.

More actions