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 keeps an editable draft, saved versions, and named releases.
Status: Alpha (features may change).
Creating a workflow
- Open Workflows and click New Workflow
- Add a trigger node (Manual Start, Schedule, Incoming Webhook, Record Created / Updated, …)
- Add action nodes and connect them by dragging from outputs to inputs
- Configure each node’s settings in the sidebar
- Save your workflow and use the version picker to switch between the Draft, the Saved version, branches, and releases
Editing the canvas
Drafts, saved versions, and releases
- Draft is your editable working copy.
- Saved is the last saved version.
- Releases are named, immutable versions you can keep for milestones or rollbacks.
- Branches let you keep variants of a workflow side by side; the version picker lists branches and releases.
- Opening the saved version or a release lets you inspect it safely without overwriting your draft. Restore it into the draft when you want to keep editing.
- Set a release active to make triggers run exactly that version. Without an active release, triggers run the saved workflow.
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 Run to execute your workflow. Watch nodes highlight as they execute, then inspect outputs by clicking completed nodes.
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
- Save the workflow after adding the webhook node - triggers sync on save
- 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)