Record clicks as code
Press Record and work in the live browser right on the page. Each click arrives in the editor as a Playwright line.
Record what you do in a browser and get Playwright code. Chain those blocks into flows that work through long lists for hours — with loops, retries and a live browser you can step into.
Six short clips of Flow Studio at work on books.toscrape.com, a public sandbox made for scraping.
Press Record and work in the live browser right on the page. Each click arrives in the editor as a Playwright line.
Say what comes next in plain words (⌘K). Claude reads the open page and writes the code at the cursor; one ⌘Z takes it back.
Select a locator and run just that line: the matches light up in the browser, and the result lists what they hold.
Set a breakpoint and step: the browser waits on the current line while you read item, global and the local variables.
A Loop sends each category through the chain while the browser shows every page — 77 books land in books.csv.
A category that is not on the site stops that item, not the run: Retry, Skip item or Debug in Codegen — then carry on.
Two services, one workflow: Codegen builds blocks — one job on a site each — and Flow runs them as a pipeline.
Click and type in the browser. Playwright code appears in the editor, line by line.
Click an element on the page and its locator — getByRole, getByLabel, getByText — goes into the code.
Describe a step in words (⌘K). Claude sees the open page and writes the code — and fixes the block after a failed run.
Breakpoints, step, continue and local variables — on the page that is open right now.
Blocks on a canvas, joined by arrows. A Loop repeats a chain for every item of a list.
What a block returns becomes the next one's item; global is shared by the whole run. Script nodes add your own JS.
Random delays, retries, pause and step node by node. On an error the run waits: retry, skip the item or debug — no restart.
Watch every run and sign in by hand right in the page. Logins stay in the browser profile between runs.
A folder per run: the log, the CSV and JSON you saved, the code of every block, a screenshot of every error.
Flow takes the blocks you saved in Codegen and runs them as a graph: arrows set the order, a Loop repeats a chain for every item, and the data moves along the arrows.
Pick blocks from Codegen in the side panel: a click adds a node and connects it to the last one. Script nodes hold your own JS in between.
A Loop goes through a list — typed into the node, returned by the previous block, or an expression like global.queries. each runs per item, done gets every result.
item is what the previous node returned. global is one object for the whole run: counters, collected lists, settings.
Run, Pause, Next, Resume. When a node fails, the run waits with the browser open: Retry, Skip item, or Debug in Codegen — then carry on.
Each run writes its folder as it goes: the log, your CSV and JSON, the exact code of every block, a screenshot and HTML of every error.
Codegen is where blocks are made — one job on a site each: sign in, search, collect a list. Record it in a real browser, shape the code, test it on sample data and save it for Flow.
Press Record and work in the browser. Clicks, typing and choices arrive as Playwright code at the cursor.
Pick elements for locators, insert ready snippets — links, tables, loops, HTTP, CSV — or ask Claude to write a step.
Give the block a sample item and global. Run it whole, or only the line under the cursor — matching elements light up in the browser.
Set breakpoints, step line by line and read the variables while the page waits.
Each save is a new version, and Flow always runs the latest. Any block also downloads as a standalone Node.js script.
Tell us which site and what you need from it — we'll show you Flow Studio doing it.
Book a demo [email protected]The button opens your email app with a short request ready to send — add the site and the task.