Skip to main content

What is a Node?

A node is a single unit of execution within a workflow. Each node performs a specific action—calling an AI model, executing a tool, transforming data, or controlling execution flow. Nodes are connected by edges to create complex automation pipelines.

Self-Contained

Each node has its own configuration, inputs, outputs, and execution logic

Visual Interface

Nodes are represented as boxes on the canvas with input/output handles

Typed Connections

Nodes connect via edges that define data flow and execution order

Real-time Status

See execution status, outputs, errors, and costs as workflows run

Node Anatomy

Handles

Nodes connect to each other through handles - connection points that define data flow:
Receive data and execution flow
  • Located on the left side of nodes
  • Accept connections from previous nodes
  • Trigger node execution when activated
  • Pass data from source node to target node
Send data to next nodesCommon output handle types:
  • PARALLEL: Main execution path (success)
  • ERROR: Error handling path (failures)
  • TOOLS: Tool calling path (LLM → Tool nodes)
  • IF/ELIF/ELSE: Conditional branching (Switch nodes)
  • LOOP: Iteration path (End → Start in subflows)
Bottom/Top handles for specific purposes
  • MEMORY (bottom on LLM): Bidirectional connection to Memory nodes
  • MEMORY (top on Memory): Connects to LLM’s MEMORY handle
  • These handles enable persistent conversation context

Node Configuration

Every node has configurable properties:
  • Name & Description: Identify the node’s purpose
  • Variable Mappings: Reference data from previous nodes
  • Type-Specific Settings: Model selection, tool configuration, conditions, etc.
  • Error Handling: How the node responds to failures

Detailed Documentation


What’s Next?