Start free
ActionIterableUpdated June 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.

FieldTypeRequiredDescription
Email
email
stringRequiredThe email address. Used as the recipient or identifier depending on context.
Event Name
eventName
stringRequired–
Timestamp (UNIX seconds)
createdAt
stringOptional–
Data Fields (JSON)
dataFields
stringOptional–
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.

Gmail → Iterable
1 Gmail triggers
Slack → Iterable
13 Slack triggers
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 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. TinyCommand handles Iterable's rate limits automatically so you don't have to throttle manually.
More actions

Other Iterable actions.

Action
Iterable Add to UserList (Bulk)
Bulk-subscribe via the lists/subscribe endpoint — accepts an array of subscribers in one call. Much faster for bulk migrations or daily syncs than per-user Subscribe to List.
Action
Get Iterable User
Returns the user record by email or userId with all data fields. The standard lookup for enrichment workflows or for "is this user in Iterable already" pre-flight checks.
Action
Iterable Send Triggered Email
Fires a specific transactional template at a user with merged data. Respects user subscription preferences. For "password reset, order confirmation" workflows where the email content is reviewed in Iterable but the trigger is external.
Action
Subscribe to List (Single User)
Single-user list subscription. For bulk operations (10+ users), use Add UserList which is much more efficient per-user.
Action
Update Iterable User
Upserts user data fields (plan, country, signup_date, lifetime_value). The state-update hook for keeping audience segmentation accurate.
Track Iterable Event in Iterable — start free