Track Event
vero.track_event
ActionEmailconnection required
Calls the Vero API with the connection's credentials.
Record an event against a user, creating the user profile first when Vero has never seen them.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Vero
- Secret shape
- the Vero auth token, or {"auth_token": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 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 name of the event. Vero treats case and underscores as the same, so 'Purchased Item' and 'purchased_item' are one event. | string | Yes | — | ≤ 255 characters | Viewed product |
id The user's unique identifier in your own product, as Vero's 'id'. | string | No | — | — | 1000 |
email The user's email address; use it when your product has no id for them yet. | string | No | — | email format | ada@example.com |
data Properties to record with the event, as a JSON object of your own keys. | object | No | — | — | {"product_name":"Red T-shirt"} |
extras Vero's reserved event fields: 'created_at' to date the event and 'source' to say where it came from. | object | No | — | — | {"created_at":"2026-01-01T00:00:00+0000","source":"mantle"} |
- At least one of id, email must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"data": {
"product_name": "Red T-shirt"
},
"email": "ada@example.com",
"event_name": "Viewed product",
"extras": {
"created_at": "2026-01-01T00:00:00+0000",
"source": "mantle"
},
"id": "1000"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
status The status code Vero echoed in its response body. | number | — |
message Vero's own message, which is 'Success.' when it worked. | string | — |
event_name The event name that was tracked. | string | — |
id The identifier the event was tracked against. | string | — |
email The email the event was tracked against. | string | — |
{
"email": "",
"event_name": "",
"id": "",
"message": "",
"status": 0
}Notes
- Vero drops a repeat of the same event, properties and user inside a three-minute window; put a unique value in 'extras.created_at' when every occurrence must be kept.
See Track Event run in a workflow.
In a technical demo we add the Vero connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.