Analytics preference

We only load Google Analytics after you opt in. You can change this choice at any time from Cookie settings.

Core Concepts

A workflow is a directed graph of nodes connected by edges. Manage workflows in the Workflows tab. Organize them in folders.

Workflows

A workflow is a directed graph of nodes connected by edges. Manage workflows in the Workflows tab. Organize them in folders. Execution flows from trigger nodes (Input, Cron, Telegram Trigger, Discord Trigger, IMAP Trigger, WebSocket Trigger) through processing nodes to output nodes. See Workflow Structure for the JSON format. Save and share workflows as Templates to reuse them across projects. Workflows can also run from the Board, where kanban cards trigger a column's workflow chain with the card's full context.

Nodes

Each node has:

  • Type – Determines behavior (e.g. llm, condition, http)
  • Data – Configuration (model, prompt, URL, etc.)
  • Inputs/Outputs – Handles for connecting to other nodes

See Node Types for the full list.

Edges

Edges connect a source node's output handle to a target node's input handle. Data flows along edges during execution.

Execution Flow

  1. Trigger – Input, Cron, Telegram Trigger, Discord Trigger, IMAP Trigger, or WebSocket Trigger node starts execution (see Triggers)
  2. Downstream – Each node receives output from connected upstream nodes; parallel execution runs independent nodes concurrently
  3. Expressions – Nodes reference upstream data via $nodeLabel.field. See Expression DSL.
  4. Output – Output node produces the final result

Expression References

Use $input for the Input node's data and $nodeLabel.field for any upstream node. Example: $llm.text references the text field from a node labeled "llm". Full syntax: Expression DSL. Use the Expression Evaluation Dialog for a larger editor with live backend preview when editing expressions.