Overview
Every node type available on the canvas, grouped by category. Each links to its full configuration reference — fields, defaults, operations/modes, and output shapes. For the conceptual model (the Node interface, the DAG, expressions), see Core Concepts: Nodes.
Triggers & Control Flow
These node types control the shape of a workflow's DAG rather than calling an external service: pausing, branching, looping, fanning in, calling other workflows, asserting outputs, and shaping synchronous webhook responses.
Data Transformation
General-purpose nodes for reshaping, computing, encoding, and extracting data between steps. Most accept {{ ... }} expressions in their config fields, resolved against steps, vars, trigger, secret, and input (see Workflows & the DSL).
HTTP, Files & Storage
Generic connectivity and I/O nodes: arbitrary HTTP/REST and gRPC calls, the universal connector node for third-party integrations, SFTP file transfer, per-tenant key-value storage, file/encoding utilities, and Cypher queries against Neo4j.
AI & Agents
The AI runtime: single-shot model calls, a tool-using ReAct agent with memory, a multi-agent orchestrator, LLM-powered branching, RAG retrieval, web search, and vision/multimodal analysis. See AI Agents & Tools for the conceptual overview, built-in tool list, and memory model — this page is the field-level configuration reference.
Documents & Media
These node types extract content from documents and images, generate or manipulate PDFs, spreadsheets, and images, and convert between text and audio. Generated files are written to the workspace file store for the run when supported; otherwise content is returned inline as base64.
Communication & Messaging
Channel-specific send and read actions for Slack, Telegram, WhatsApp, Instagram, Twitter/X, Microsoft Teams, email, and RSS feeds. These are workflow steps — for inbound events (new Slack messages, Telegram updates, incoming emails), see the corresponding poller triggers in Triggers.
DevOps
Infrastructure-automation node for running configuration-management and provisioning tasks as part of a workflow. Today this is a single node type — ansible — designed to be combined with the code node, the agent's terminal/file tools, and infrastructure connectors (GitHub Actions, SSH) to build CI/CD-style and ops-automation pipelines.
LiveKit & Voice Agents
LiveKit provides the real-time audio/video transport (rooms, participants, SIP, recording) behind OrcFlows' voice features. Voice agent nodes combine STT (speech-to-text), an LLM, and TTS (text-to-speech) into a real-time conversational loop that joins a LiveKit room as a participant. For starting a workflow from a LiveKit event, see Triggers — LiveKit; the underlying webhook is documented in Provider webhooks.