Studio is where you build and run browser flows: a canvas editor in the spirit of n8n, made for automations that drive a real browser (𝕏, Shopee, any site) with AI steps and a human in the loop.
In this section
| Page | What it covers |
|---|---|
| Editor | Canvas, adding and connecting nodes, notes and groups, shortcuts, command palette |
| Layout and windows | Canvas tabs, the activity bar and sidebar, right and bottom areas, windows, moving and hiding them |
| Node details | Parameters, settings, input and output panels, expressions, pinned data |
| Expressions | {{ nodes.x.output.y }}, vars, now, and the pipe helpers |
| Running a flow | Test vs real runs, the run bar, logs, output, retry, partial runs |
| Live preview | Watching and controlling the run's browsers, browser tabs, opening a browser before a run |
| Triggers | Manual, Schedule, Webhook and Form |
| Flow composition | Flow input, Return, Run flow, called flows in their own browser, Convert to flow |
| Flow settings | Run time limit, timezone, callers, error flow, tags, agent instructions |
| Versions | Draft vs published, Publish, version history |
| Tests | Evaluations: input, expected Return output, Run all |
| Packages | Export and import a flow with what it needs |
| Editing together | Live editing, who's here, your own undo, offline, read only |
| Sharing a flow | Roles on a flow, the share dialog, general access, guests, the flow's link and request page |
| Canvases | Main and your own canvases, agent drafts, locks, colors, Keep (Squash / Merge / Rebase), node context |
| Comments and suggestions | Threads, @mentions, resolve; Suggesting mode (a draft for review), accept |
| AI agent | Ask / Plan / Agent modes, live edits in its draft, Changes bar, autopilot |
The flow list
Studio (/app/<workspace>/studio) lists the flows you can open (Sharing a flow) in a table (name, published version, last edit with who made it, avatars of who has it open now) that loads the next 20 as you scroll.
- New flow — name a blank flow, Import file (a ), or start from a (a paginated grid, 6 per page, with Customize prompts).
- Filters — search by name, filter by Tag, and All / Owned by me / Shared with me / Favorites.
- Select several — tick flows (or the header box for every loaded one): a bar shows how many are picked, with Export package (one file with all of them and what they call) and Delete (asks first; stops at the first one it can't delete). Clear drops the selection.
- Row actions — Open, Star / Unstar (stars are yours only), Export package, Move or copy to another workspace you're in (), Delete (removes the flow, its versions, tests and agent conversations; past runs stay on the engine).
Inside a flow
The flow page (/app/<workspace>/studio/<id>) has one header row: back, the flow's name, sync status and who's here on the left; Search actions… (⌘K), the run controls (Test run, Run, or the active run's status with Pause / Resume / Stop), Share and Publish (its menu shows the live version and opens Version history) on the right.
Below it, the canvas sits in the middle with its open canvases as tabs, and every other part of the editor is a window in one of three areas: Canvases on the left (the activity bar), Agent, Comments, Version history, Chat, Tests and Settings on the right, Logs, Preview, Output, Stacks and Runs at the bottom. Show, hide, reorder and move them from each area's rail; see .
Concepts in one minute
| Term | Meaning |
|---|---|
| Flow | A graph of nodes and edges, with settings. You edit a draft; Publish makes a version live for triggers. |
| Node | One step. Has fields, settings and output dots. See . |
| Edge | Connects an output dot to the next node. |
| Run | One execution on the engine, in a real browser. Test run simulates effect nodes; a real run doesn't. |
| Browser | A persistent Chrome profile on the engine, named (x, shopee…) and owned by a campaign (or by the flow, in tests). |
| Intervention | The run waits for you in the live view (sign in, captcha, approval). |
FAQ
Do I need to publish before running?
No. Runs from the editor use the draft. Schedule, Webhook and Form triggers use the published version.
Where are my runs stored?
On the engine of the flow (Studio tests, triggers) or of the campaign that ran it. Runs are kept 90 days.