Track Event
iterable.track_event
ActionEmailconnection required
Calls the Iterable API with the connection's credentials.
Record one custom event against a user profile.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Iterable
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- region, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
9 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
event_name The event name, as it should appear in Iterable. | string | Yes | — | — | — |
email The email address that identifies the user. Provide this or 'user_id'. | string | No | — | email format | — |
user_id The userId that identifies the user. Provide this or 'email'. | string | No | — | — | — |
data_fields Custom fields to store, as a JSON object. Iterable merges them into the profile. | object | No | — | — | — |
event_id Your own event id. Re-sending the same id updates that event. | string | No | — | — | — |
created_at When the event happened, as a Unix timestamp in seconds. Iterable uses the time of receipt when this is empty. | integer | No | — | ≥ 0 | — |
campaign_id Campaign to attribute the event to as a conversion. | integer | No | — | ≥ 1 | — |
template_id Template to attribute the event to. | integer | No | — | ≥ 1 | — |
create_new_fields Add data fields the project schema does not know yet. | boolean | No | — | — | — |
- At least one of email, user_id must be set.
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
code Iterable's response code, 'Success' when the call was accepted. | string | — |
msg The human-readable message Iterable returned. | string | — |
params Any extra detail Iterable attached to the response. | object | — |
accepted True when Iterable queued the event. | boolean | — |
event_name The event name that was sent. | string | — |
{
"accepted": false,
"code": "",
"event_name": "",
"msg": "",
"params": {}
}Notes
- Events are processed asynchronously, so a success means queued, not stored.
- Single and bulk tracking are separate pipelines — send a stream of events through one or the other, or their order is not preserved.
See Track Event run in a workflow.
In a technical demo we add the Iterable connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.