Nodes and edges
Each workflow is a directed graph: nodes (steps) linked by edges (data and control flow).
💡 Node anatomy
- Input: payload from parent node or trigger.
- Output: JSON object merged into the run context.
- Inspector: business form, advanced JSON, reliability (retry, idempotency key).
💡 Edges: canonical format
Knot stores links as source / target (port ids on the canvas). Legacy import may use from / to; the editor normalizes to the canonical format on save.
💡 Node families
| Family | Role | Examples |
|---|---|---|
| Trigger | Starts the run | Manual, Cron, Webhook, object event |
| Logic | Branch, loop, wait | If/Else, Switch, Loop, Delay |
| Action | Side effect | Dolibarr, HTTP, Email, AI |
| Utility | Transform context | Set, Filter, Merge |