volanea_track_event
Send a product event exactly as the user's app would (POST /v1/events). Auto-creates the contact if unknown, and SYNCHRONOUSLY fires any workflow whose trigger is event:<name> plus any matching webhooks — so this is how you verify an event-triggered automation for real. Also useful to seed a test contact — but note that a contact created this way is tagged as a test artifact and is EXCLUDED from segment evaluation and campaign audiences, so it will never appear in a volanea_create_segment dryRun count or a campaign's recipient list, whatever its fields say. System prefixes (email./contact./segment./workflow.) are reserved.
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": {
"name": "<name>",
"email": "<email>"
},
"name": "volanea_track_event"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Event payload; available to workflows as {{variables}}. | |
| name | Yes | Event name, e.g. "user.signed_up". Use the same name the app will send. | |
| Yes | Contact's email address. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | Machine-readable failure code to branch on. Present only when success is false. | |
| data | No | Present when success is true. | |
| error | No | Human-readable failure reason. Present only when success is false. | |
| success | Yes | False when the call failed; read `error` and `code` in that case. |