Track event
track_eventRecord something a customer did (e.g. signed_up, cart_abandoned, trial_ending), by user_id and/or phone. It starts or advances any active automation listening for that event. external_id (their Mixpanel distinct_id, when not user_id) puts the texts it starts on their Mixpanel profile.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"event": "<event>"
},
"name": "track_event"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| event | Yes | Letters, digits, and _ . : - | |
| phone | No | The person's number in E.164 | |
| user_id | No | Your id for the person. Sent with phone, it links the two, so later events need only user_id | |
| properties | No | Up to 20 scalar values; usable as merge fields and in conditions. | |
| external_id | No | Optional. The person's id in your analytics tool (their Mixpanel distinct_id; `mixpanel_distinct_id` is accepted too), when it is not user_id. Kept on the event as mixpanel_distinct_id; texts the event starts land on that profile in Mixpanel. Without it, user_id is used. | |
| idempotency_key | No | Optional. A unique key for this call: a retry with the same key is recorded once. |