Workflow Nodes Reference

Complete reference for every node type available in the Agentic Designer. Each node performs a specific role in your workflow graph — from LLM calls and branching logic to state management and safety checks.

Template Variables

Many node fields support template variables that resolve at runtime. Use double-brace syntax inside any field marked with “supports templates”.

Node Overview

Start Node

Every workflow must have exactly one Start node. It is the entry point that receives the user’s input and optionally initializes global state keys for downstream nodes.

Settings

Outputs

Produces the bound user input as its output and connects to the first processing node via its out handle.

End Node

Terminates workflow execution and produces the final output returned to the caller. Every workflow must have at least one End node.

Settings

LLM Node

Calls a large language model with a configurable prompt. The prompt template supports all template variables, so you can inject state, previous outputs, or user input dynamically. The model is selected via your router configuration.

Settings

Advanced

Timeout, On Error (fail run, continue, or go to node), and Disabled toggle are available under the Advanced section for all execution nodes.

Agent Call Node

Delegates a sub-task to another agent you own. The child agent executes its own full workflow and returns its output. Supports cycle detection, call-depth limits (max 5 levels), and cost guardrails.

Settings

If Node

Evaluates a condition and routes execution to either the true or false output handle. Supports both simple comparisons and JSON Logic expressions. Both modes fully support dynamic state and template variables.

Condition Types

Simple Compare

Compares a left operand against a right operand using an operator. Both operands support template variables, so you can branch on dynamic runtime values.

Example: To check if a counter exceeds 5, set Left Operand to {{state.counter}}, Operator to >, and Right Operand to 5.

JSON Logic

A JSON object evaluated using JSON Logic rules. Use the var operator to reference runtime data.

Available data paths for var:

// Check if state.counter > 5
{ ">": [{ "var": "state.counter" }, 5] }

// Check if last output contains "approved"
{ "in": ["approved", { "var": "last_output" }] }

// Combine conditions with "and"
{ "and": [
  { ">": [{ "var": "state.counter" }, 0] },
  { "!=": [{ "var": "state.status" }, "done"] }
] }

Supported operators: ==, !=, >, <, >=, <=, and, or, !, in, var.

Advanced

Handles

Connect the true handle to the path that executes when the condition passes, and the false handle to the alternative path.

While Node

Evaluates a condition on each pass. If true, routes to the loop handle; if false, routes to exit. The loop body must eventually connect back to this While node to form the cycle. Uses the same condition types as the If node (Simple Compare or JSON Logic).

Settings

Handles

loop — connects to the first node in the loop body. exit — connects to the node that runs after the loop finishes.

User Approval Node

Pauses the workflow and waits for a human to approve, reject, or let the request time out. The decision routes execution to one of three output handles: approved, rejected, or timed_out.

Settings

Handles

approved — the approver accepted. rejected — the approver declined or the request auto-rejected on timeout. timed_out — only active when On Timeout is set to route_timeout.

Global State Node

Performs read/write operations on the run’s key-value state store. Use this to set counters, flags, accumulators, or any data that other nodes need to read via {{state.key}} template variables or the var operator in JSON Logic conditions.

Settings

Data Transform Node

Transforms data using a template expression or JSONata query and writes the result to a state key. Useful for reshaping LLM output, extracting fields, or building structured payloads between nodes.

Settings

Guardrails Node

Scans content for personally identifiable information (PII) and other sensitive patterns. Can warn, block execution, redact matches, or route based on whether content is flagged.

Settings

Handles

When Action is route_by_result, the node exposes flagged and pass handles. Otherwise it has a single out handle.

Note Node

A canvas-only annotation. Notes are not executed at runtime and have no input or output handles. Use them to document your workflow, leave reminders, or explain complex logic to collaborators. Notes support inline editing directly on the canvas.

Common Advanced Settings

Most execution nodes (LLM, Agent Call, While, Data Transform, Guardrails) share the following advanced settings: