Skip to content
Octo

Node Reference

Nodes are the building blocks of an AI Workflow graph. Each node performs one job, exposes configuration in the inspector, and connects to other nodes through ports.

Node choice becomes easier when you think in terms of workflow jobs. Some nodes start or end execution, some reason with language, some transform or fetch data, and some route the flow to the next step.

How to choose a node

Section titled “How to choose a node”

Choose a node based on what the workflow needs to do at that point:

  • Use Start when the branch should begin.
  • Use AI Agent when the workflow needs language reasoning, tool judgment, or dynamic routing.
  • Use AI Extraction when the workflow should turn natural-language input into structured fields.
  • Use Tool or Function when the workflow must execute a deterministic action.
  • Use If/else when branching should be explicit and reviewable.
  • Use Wait, Play, or Transfer when the workflow must handle a specific voice or control-flow moment.
  • Use End when a branch should stop cleanly.

Core nodes

Section titled “Core nodes”
  • Start begins workflow execution automatically.
  • AI Agent handles conversational reasoning, tool use, and exit-condition branching.
  • AI Extraction pulls structured fields from conversation context.
  • Wait pauses execution until the next message or event.
  • End terminates a branch cleanly.

Action nodes

Section titled “Action nodes”
  • Tool calls a configured REST API or Script tool.
  • Function runs custom JavaScript logic inside the workflow.
  • Play plays a voice message to the caller in voice workflows.

Logic nodes

Section titled “Logic nodes”
  • If/else evaluates configured conditions and routes to the matching path.
  • Transfer hands a voice conversation off to a configured contact or SIP endpoint.

How nodes connect

Section titled “How nodes connect”
  1. Every workflow starts with the automatic Start node.
  2. Connect output ports to input ports by dragging between nodes.
  3. Each output port supports one outgoing connection.
  4. AI Agent and If/else nodes can create dynamic output ports from configuration.
  5. Every active branch should either continue to another node, transfer, wait intentionally, or end.

Common node combinations

Section titled “Common node combinations”
  • Reason, then act Use AI Agent -> Tool -> AI Agent when the workflow must interpret a request, call a system, then explain the result.
  • Extract, normalize, and route Use AI Extraction -> Function -> If/else when free-form user input must become structured before branching.
  • Deterministic branch and action Use Function -> If/else -> Tool when the route depends on a computed value and each branch performs a known action.
  • Prompt, pause, continue Use Play or AI Agent -> Wait -> the next step when the workflow must pause for the next user reply.
  • Escalate safely Use AI Agent or If/else -> Transfer -> End when the workflow should hand a voice conversation to another destination and stop automation.

FAQ

Section titled “FAQ”

Are stencils and nodes the same thing? In the builder, stencils are the draggable definitions. Once placed on the canvas, they are nodes in the workflow graph.

Does the Start node need configuration? Usually no. It marks where execution begins and only needs a readable label when a workflow has multiple reviewers.

Section titled “Related pages”