Node Types

Every workflow in Builder Studio is built from nodes. Each node is a typed unit on the canvas with its own data, ports, and behavior. This page groups the node types by what they do and links to the reference page for each one.

Content nodes

Content nodes hold text you author directly. They are how a workflow starts with words instead of a model call.

• Prompt — structured text input for reusable prompts and upstream instructions. Outputs its text so downstream generation and processing nodes can consume it.
• Text — a static text layer for literals, notes, and labels placed directly on the canvas. It is a visual layer, not a runtime input.

AI generation and agent nodes

Generation nodes call a model provider to produce new content. They expose provider, model, and parameter controls and report status while they run.

• Text Generation — general text generation for reasoning, chat, summarization, or code output, with streaming results.
• Image Generation — image synthesis with provider-bound presets and generic image generation paths.
• Video Generation — image-to-video and text-to-video flows.
• Audio Generation — speech and voice generation for narrated output.
• SFX Generation — non-voice sound effect generation.
• 3D Generation — 3D asset generation, with provider-locked Tripo and Meshy variants of the same surface.
• Agent — a longer-running agent runtime with tool use and traces.

Media nodes

Media nodes store or display media that already exists — uploads and generation outputs — and preserve a reference downstream nodes can reuse. They do not call a model themselves.

• Image — upload, crop, export, and reuse image files.
• Video — play, sync, and reuse video files with custom playback controls.
• Audio — play, sync, and reuse audio files with custom playback controls.
• 3D Model — display generated or uploaded 3D assets with interactive orbit controls.

Logic and control nodes

Logic nodes shape how a workflow flows — branching, combining, pausing, and repeating.

• Conditional — branch workflow logic based on upstream values.
• Merge — combine multiple upstream branches into one downstream flow.
• Delay — pause execution for a specified duration.
• Loop — iterate over a collection or repeat a sub-flow.

Utility and integration nodes

Utility nodes connect a workflow to the outside world or transform data as it passes through.

• Webhook Call — make outbound HTTP requests to external APIs.
• Webhook Trigger — create a dedicated HTTP entrypoint that starts a workflow.
• OpenClaw Trigger — start a workflow from OpenClaw and Telegram-linked inbound events.
• Transcribe — turn audio input into text output.
• Browse Web — fetch, screenshot, and extract content from web pages.
• HTML Viewer — render sandboxed HTML output directly on the canvas.

MCP Server Builder nodes

These node types are used inside the visual MCP server builder to define the tools, outputs, and credentials a published user MCP server exposes.

• MCP Tool — define a workflow-backed tool surface a published MCP server can expose.
• MCP Output — select the workflow value the published tool returns.
• MCP Credential — configure an encrypted credential surface for tool handlers.