Workflow Builder Overview
How Triggo workflows work — canvas, nodes, edges, and the draft/active lifecycle.
Workflow Builder Overview
A workflow in Triggo is a small program you assemble visually. This page explains the pieces and how they fit together.
What a workflow is
A workflow is a directed acyclic graph (DAG): a set of nodes that do the work, connected by edges that route data between them. "Acyclic" means a node never feeds back into one of its own ancestors — data always moves forward.
When a workflow runs, the executor walks the graph in topological order using Kahn's algorithm. Every node waits for its parents to finish before it starts, so you can reason about a workflow as a sequence of steps even when branches run side by side.
The canvas
The canvas is where you build the workflow. You drag nodes in from the side panel and connect them by drawing edges between their handles. Selecting a node opens its inspector, where you fill in its configuration — credentials, fields, conditions.
The canvas always shows the draft version of the workflow. Edits you make on the canvas don't affect a running workflow until you publish them.
Node categories
Triggo has four kinds of nodes:
- Trigger — exactly one per workflow. The trigger starts every run. It can be a webhook, a scheduled time, or an event from an external service. See triggers.
- Connector actions — call out to external services (AmoCRM, Telegram, Google Sheets, and the rest of the catalog). One node, one operation.
- System nodes — building blocks that don't talk to a single integration: Loop, Condition, HTTP request, and similar flow-control primitives. (Dedicated reference page in progress — see the Code node docs meanwhile.)
- Code node — run JavaScript or TypeScript when no built-in node fits. See code node.
Edges and data flow
Edges carry data from a parent node to its children. A child node can reference the output of any ancestor — not just its direct parent — by name. Use the field mapping editor in the inspector to wire values through; see field mapping for the syntax.
If a node is unreachable from the trigger, it never runs. If a branch is skipped (for example, by a Condition node), its descendants are skipped too.
Draft vs active
Every workflow has two faces:
- The draft is what you edit on the canvas. Changes are saved as you go but have no effect on production.
- The active version is the one that actually runs when the trigger fires. Only one version can be active at a time.
To promote your draft, click Publish in the canvas toolbar. Triggo snapshots the current draft as a new version and makes it active; the previous active version is kept in history so you can roll back. See activation and versioning for the full lifecycle.