Visual Workflow Builder

Visual Builder is the V1-style canvas for a workflow that needs a whole-flow view or a TRUE/FALSE branch. It is available at 1024px wide and above. Smaller screens use Guided Editor, and the native mobile app remains unchanged.

Open the canvas

Create or edit a workflow in Guided Editor, then choose Open Visual Builder on a desktop screen. The canvas edits the same draft revision. A template is cloned into a draft before it can be changed; see Templates.

Teammates with Automations view can inspect a graph. Automations manage is required to add, move, configure, connect, save, test, activate, pause, or rename it. The server repeats the permission, organization, and location-scope checks when a mutation is submitted.

Canvas layout

• Step Palette: searchable, grouped step definitions. Drag a step onto the

canvas to add a node.

• Canvas: pan with the work area, zoom with the toolbar, and connect node

handles. A dot grid and the minimap help with larger graphs.

• Config Panel: select a node to edit its action or condition fields. The

panel validates the same bounded payload that the server accepts.

• Toolbar: workflow name, zoom in/out, Fit Workflow, Reset View,

Auto Arrange, minimap toggle, Guided Editor, Test, Save, and Activate/Pause.

When positions are missing or invalid, Auto Arrange lays out the graph from top to bottom. An ordinary ordered path stays in one column; TRUE and FALSE branches are placed on separate sides of their condition.

Connect and branch

Drag from an action's default handle to the next node. A condition exposes TRUE and FALSE handles; the edge label is kept with the branch so the path remains understandable after moving nodes. A condition can use All or Any logic for its bounded condition list.

The graph must be a directed acyclic graph. It allows up to 200 nodes and 400 edges. An action has one default outgoing edge, while a condition must provide its true and false paths. Cycles, missing references, malformed payloads, and unsupported node types are rejected when activating. Incomplete drafts may be saved while they are being built.

The older V1 split and recurring-schedule steps are intentionally unavailable in W11. They are not safe aliases for condition nodes.

Timing and Internal Notes

In a new visual workflow, Wait uses minutes, hours, or days and keeps the workflow's business-hours settings. Older linear workflows keep their existing weeks, anchored waits, and team-notification behavior. When an older workflow uses a calendar anchored wait, Visual Builder shows that step and preserves it when the draft is saved. Its calendar anchor is kept intact rather than being converted into a duration delay; use Guided Editor to change that wait.

Guided draft saves work with Wait and Internal Note. Internal Notes stay in the conversation, while team notifications keep their configured recipients. New workflows save correctly even when other workflows already exist. If an incompatible change is made, the editor keeps the unsaved edits and shows a clear error.

Saved Guided workflows reopen with their Wait and Internal Note steps still visible.

Step availability

The current visual bridge exposes these V1-style steps:

• Send SMS
• Send email
• Delay
• Condition
• Add tag
• Remove tag
• Internal note
• Create task

The canonical W11 graph contract also defines calls, voicemail drops, status updates, user assignment, field updates, webhooks, workflow enrollment or removal, and award_xp. Those types require their matching adapter and executor in the build being reviewed. Their presence in the contract or this documentation does not claim that a provider is configured or that the action is deployed.

Save, test, and activate

The canvas autosaves a changed graph after a short debounce and shows an explicit dirty, saving, saved, or error state. Save forces an immediate save. The graph uses an expected revision and a request generation, so a late response cannot overwrite a newer draft. A revision conflict leaves the local canvas intact and exposes Reload latest; that button asks for confirmation before it replaces the canvas with the server graph. The viewport is advisory and is stored separately from the executable graph.

Test is provider-free. For a straight workflow, the preview follows the workflow order. If sample data cannot run a step, the preview identifies that step with a clear warning instead of inventing a result. For branches, the preview lists the steps but does not execute branch conditions.

Activate validates the complete graph and publishes the exact draft revision that was reviewed. If another teammate saved first, reload the latest revision and review it before retrying. Runs already enrolled stay pinned to their published revision.

Webhook nodes render stored URL, header, and body values as [saved securely] with opaque unchanged-save references. The canvas never receives the raw secret value. Voice nodes remain pending until a signed, account-bound provider callback settles their durable reservation; a callback status alone does not mark the graph node successful.