Nodes

Complete reference for all node types in Workflow Builder

Nodes are processing units within a workflow that execute specific tasks. Each node has distinct configuration and functionality.

Start Node

The workflow entry point. Every workflow must begin with this node.

Configuration:

  • Test Prompt: Input for testing workflow in preview mode

Rules:

  • Cannot be deleted or renamed
  • Only has output handle (right side)
  • Required in every workflow

Agent Node

AI node with custom system prompt that processes input and generates responses.

Configuration:

  • Node Name: Agent identification name
  • Input Source Expression: CEL expression to retrieve input data (default: input)
  • Instructions: System prompt for the agent
  • Output Format: Text or JSON (with optional JSON Schema)
  • Send Output to Chat: Toggle to send output to chat interface
  • Load Conversation History: Toggle to load conversation history as context
  • Save to Conversation History: Toggle to save responses to history

Usage:

  1. Set a descriptive Agent Node name
  2. Write instructions according to desired task
  3. If structured output is needed, select JSON format and define schema
  4. Enable conversation history if agent needs previous conversation context

Condition Node

Logic branching based on CEL expression evaluation. Has multiple output handles.

Configuration:

  • Conditions: List of if/else-if conditions
    • Case Name: Condition label (optional)
    • Expression: CEL expression (example: input.score > 80)
  • Else Branch: Output for unmet conditions

Usage:

  1. Click "Add" to add new condition
  2. Write CEL expression (example: input.status == "completed")
  3. Connect each output handle to different target nodes
  4. Conditions are evaluated sequentially, first true condition executes

Expression Examples:

  • input.amount > 1000
  • input.category == "urgent"
  • input.score >= 80 && input.score < 90

Search Internet Node

Search for information from the internet using Google Custom Search API.

Configuration:

  • Input Source Expression: CEL expression for search query
  • Output Expression: Transform search results before passing forward

Usage:

  1. Ensure Google API Key and CX are configured in Settings
  2. Set expression for query (default: uses previous node output)
  3. Output contains search results and sources

Note: Requires valid API credentials.

Read Document Node

Read content from local files (PDF, DOCX).

Configuration:

  • Input Source Expression: CEL expression for file path
  • Output Expression: Transform file content before passing forward

Usage:

  1. Set expression to get file path (example: input.file_path)
  2. Node will extract content from file
  3. Supports formats: PDF, DOCX

Example: "C:\\Documents\\report.pdf" or input.document_path

Search Memories Node

Query from vector database memories using semantic search.

Configuration:

  • Input Source Expression: CEL expression for search query
  • Output Expression: Transform query results before passing forward

Usage:

  1. Set expression for query (default: previous node output)
  2. Node will search in LanceDB vector store
  3. Output contains relevant semantic search results

Note: Ensure data exists in memories database.

Call Command Node

Execute shell commands in the operating system.

Configuration:

  • Input Source Expression: CEL expression for command to execute

Usage:

  1. Set expression for command (example: "dir C:\\Users" or input.command)
  2. Command executes in PowerShell or Bash

Warning: Be cautious with dangerous commands. Use User Approval before this node for validation.

Call API Node

Call external HTTP APIs.

Configuration:

  • Method: GET, POST, PUT, PATCH, DELETE
  • URL: API endpoint
  • Headers: Custom headers (JSON format)
  • Body: Request body for POST/PUT/PATCH
  • Output Expression: Transform API response

Usage:

  1. Select HTTP method
  2. Enter endpoint URL
  3. Set headers if needed (example: {"Authorization": "Bearer token"})
  4. For POST/PUT, fill body with JSON data
  5. Output contains API response

Send Response Node

Send response to user through chat interface.

Configuration:

  • Response Message: CEL expression for message to send

Usage:

  1. Set expression for message (example: "Task completed: " + input.result)
  2. Message is sent to chat interface
  3. Can concatenate text with data from previous node

Example: "Found " + string(input.count) + " results"

User Approval Node

Request user approval before continuing workflow. Dialog appears with Approve/Reject options.

Output Handles:

  • Approved (green): Continue if user clicks Approve
  • Rejected (red): Continue if user clicks Reject

Usage:

  1. Connect node before critical operations (delete, command, API call)
  2. When workflow reaches this node, approval dialog appears
  3. User reads context and chooses Approve or Reject
  4. Workflow continues according to user choice

Use Case: Confirmation before deleting files, executing dangerous commands, or API calls that modify data.

End Node

Terminate workflow. Workflow stops when reaching this node.

Rules:

  • Cannot be deleted or renamed
  • Only has input handle (left side)
  • Multiple End nodes allowed for various exit points

Note Node

Workflow documentation. Not executed, for notes only.

Configuration:

  • Note: Note text for documentation

Usage:

  1. Drag Note node to canvas
  2. Fill with notes, logic explanations, or reminders
  3. Node is not connected and does not affect execution

Use Case: Document complex logic, TODO notes, explanations for other developers.

On this page

Start NodeAgent NodeCondition NodeSearch Internet NodeRead Document NodeSearch Memories NodeCall Command NodeCall API NodeSend Response NodeUser Approval NodeEnd NodeNote Node