Visual Workflows

Workflows are Rollout's automation control plane. Build business processes by connecting triggers, AI, code, integrations, client-device actions, and utility nodes on a visual canvas. The editor continuously autosaves your Draft; publishing freezes it as an immutable, automatically numbered Release for production.

Status: Alpha (features may change).

Creating a workflow

  1. Open Workflows and click New Workflow
  2. Add a trigger node (Manual Start, Schedule, Incoming Webhook, Record Created / Updated, ...)
  3. Add action nodes and connect them by dragging from outputs to inputs
  4. Configure each node's settings in the sidebar
  5. Click Test to try the current Draft, then click Publish workflow when it is ready for production

Editing the canvas

Draft, Publish, and Current Release

  • Draft is your editable working copy. Canvas and settings changes autosave continuously, but the Draft is never a production target.
  • Publish validates the exact visible Draft, creates the next immutable Release (v1, v2, ...), and makes it the Current Release in one operation.
  • Current Release is the only source for new production runs. If a workflow has not been published, it has no production target.
  • Running allows triggers to start new production runs from the Current Release. Paused rejects new production entries without changing the Current Release or interrupting runs already in progress. A workflow's first Publish leaves it Paused so you can review it before clicking Start.
  • Publishing changes while a workflow is Running switches new runs to the new Current Release. Runs already admitted keep the release and execution settings they started with.
  • Branches let you develop variants side by side. Each branch has its own autosaved Draft; publishing a branch creates the next workflow-wide Release and records which branch it came from.
  • Release history is read-only. Open a Release to inspect it, use Restore to make that Release Current without changing your Draft, or use Copy to Draft from a run when you want to edit what that run used.

Disabled nodes and edges remain visible in the Draft and in published history, but they are excluded from execution. A disabled trigger cannot start a run, a disabled action is not scheduled, and a disabled edge does not carry execution to its target.

Organizing larger flows

  • Select two or more nodes and click Group to put them in a canvas container. Ungroup dissolves it.
  • Use Auto Layout to tidy larger graphs. Layout and edge routing run on the server, so everyone sees the same arrangement.
  • Text settings support {{ }} templates. Use Insert variable to pick outputs from the trigger or any upstream node without retyping handle names. Templates also support expressions: comparisons, arithmetic, and functions.

Running workflows

Click Test to execute the current Draft as a debug run. The editor first autosaves the exact visible graph, then runs that Draft even when production is Paused. Watch nodes highlight as they execute, then inspect outputs by clicking completed nodes.

For an on-demand production run, publish a workflow that contains an executable Manual Start trigger, click Start, then use Run now from the Workflows list. Production runs always use the Current Release.

Run types

  • Full run - execute the whole workflow from the trigger
  • Step run - execute a single node for testing
  • Subgraph run - execute a node and everything downstream of it
  • Retry run - re-run a previous run with the same inputs

Debug mode

Runs started from the editor are debug runs by default. Use the Show debug runs filter in history to toggle their visibility.

Action nodes

Core actions

  • API Request - call any REST API with query params, headers, auth, and body editors
  • Code Execution - run JavaScript in a sandbox
  • AI Agent - prompt an AI model with structured output and optional tool calling; pick a managed model (Gemini by default) or bring your own provider key through a Connection
  • Query Data - query tasks, projects, objectives, milestones, teams, activities, and custom records with filters
  • Query Saved View - pull records from a saved view's query
  • Search - retrieve tasks, projects, documents, records, and attachments by keyword
  • Perplexity Search - web research with citations (requires a server API key)
  • Send Mail - send email via the configured mailer
  • File Convert - convert and merge files (HTML, text, images, PDFs) into a PDF bundle
  • Subflow - call another workflow and return its outputs
  • Loop - run a workflow repeatedly until an exit condition or an iteration cap

Record and document actions

  • Create Record, Update Record, Delete Record
  • Attach Resource and Identify Resource
  • Create Document and Update Document - rich-text documents from markdown
  • Create Activity

Integration actions

  • Gmail - send, reply, search, get, update, manage labels, archive, trash
  • Sheets - read, append, update, clear
  • Drive - upload, download, search, move, create folders
  • Jira - create, update, get, search, comment, transition issues
  • GitHub - open, get, and list pull requests
  • Telegram - send messages and parse updates

Delivery actions

  • Shell - execute shell commands in the workflow runtime
  • Git - branch, checkout, commit, push, tag
  • Docker Build and K8s nodes - build images, apply manifests, set images, run jobs, watch rollout status

Device actions (experimental)

  • Run Command - run a shell command on a connected device
  • Claude Code and Codex - run coding-agent tasks on a connected device
  • Browser Automation - run Playwright scripts in a connected Chrome session

Control flow and utility

  • If - route to true/false outputs on a condition expression
  • Switch - route across named outputs by expression cases
  • Merge - combine any number of inputs (concat, first, or object)
  • Wait - pause the run for a duration or until a timestamp
  • Human Input - pause the run until a person responds to a prompt
  • Stop - end the run as a success; downstream nodes never run
  • Fail - fail the run with an authored error message
  • Map / Transform - reshape, filter, sort, aggregate, and join lists without code
  • Cache Save / Restore - cache workspace files between runs
  • Note - annotate the canvas

See Node Reference for a full list and status notes.

Execution details

Parallel execution

Full runs can execute independent branches in parallel (up to 10 concurrent steps by default).

Timeouts and retries

  • Runs time out after 30 minutes by default; each workflow can configure 1-180 minutes
  • Failed runs retry with exponential backoff (10s, 20s, 40s; max 3 attempts)

Retention

Workflow runs are archived after 30 days and permanently deleted 90 days after archival.

Troubleshooting

Workflow not triggering from webhook

  • Verify you are hitting the correct URL
  • Publish the Draft after adding the webhook node
  • Verify the webhook trigger node is not disabled and the workflow is Running
  • A 429 response means the webhook is rate limited; retry later

Cannot connect two nodes

  • The canvas rejects connections between incompatible output and input types
  • Pick a source port whose type matches the target input

API Request returning errors

  • Check the URL, method, and headers
  • Verify authentication credentials
  • Inspect the response body for error details

Gmail trigger not finding new email

  • Verify your Google connection is active
  • Check the trigger's filters are not too restrictive

AI Agent returning errors

  • Verify the prompt is not empty
  • Check for rate limiting from the provider
  • Try a smaller prompt if hitting token limits

Run stuck in "running" state

  • Check for nodes with long timeouts
  • Look for external API calls that might be hanging
  • Runs time out automatically after the workflow's run timeout (30 minutes by default)