validate_automation
Validate an automation graph without saving it to catch unknown node types, missing settings, CEL type errors, and broken edges; fix issues before creating the automation.
Instructions
Check a graph without saving it: unknown types, missing settings, CEL type errors, broken edges. Fix every problem; with none, save it with create_automation. A graph is {"nodes":[…],"edges":[…]}, a tree from exactly one trigger. Nodes: {"id","kind","type","config"}; kind is "trigger" (type: a trigger key, id "trigger"), "action" (type: an action key) or "condition" (no type; config {"cel": "<CEL expression over the trigger's fields>"}). Edges: {"from","to"} in the order nodes run; edges leaving a condition carry "branch": "true" (Yes) or "false" (No). Settings marked placeholders accept {{field.key}} from the trigger's fields, e.g. "{{license.id}}". CEL is typed: compare ints with ints (license.machinesUsed > 2), doubles with doubles (2.0), timestamps with timestamp("2026-01-01T00:00:00Z") or now ± duration("72h"); string fields with options only take those values.
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": {
"graph": "<graph>"
},
"name": "validate_automation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| graph | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| valid | Yes | no problems: it can be saved, tested and switched on | |
| problems | No |