update_automation
Modify an automation's name, description, or full graph while keeping existing nodes in place and checking that enabled automations remain valid before the next run.
Instructions
Change an automation's name, description or whole graph. Nodes that keep their id keep their place on the canvas. An automation that is switched on must stay free of problems, and the change applies to its next run: confirm with the user first. 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": {
"automation": "<automation>"
},
"name": "update_automation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | a new name | |
| graph | No | the whole new graph (get_automation shows the current one); left out keeps it | |
| automation | Yes | the automation's id or name | |
| description | No | a new description; empty string clears it |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| next | Yes | what to do next | |
| automation | Yes |