Get User Events
iterable.get_user_events
ActionEmailconnection required
Calls the Iterable API with the connection's credentials.
List the most recent events recorded for one user.
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
3 fields, none 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 |
|---|---|---|---|---|---|
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 | — | — | — |
limit How many events to return. Iterable defaults to 30 and caps this at 200. | integer | No | 30 | 1–200 | — |
- At least one of email, user_id must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"limit": 30
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
events The events Iterable returned, newest first. | array | — |
count How many events were returned. | number | — |
{
"count": 0,
"events": []
}See Get User Events 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.