You already know how to do the task: open the portal, fill the form, search, pick, book. Flow Recorder sits quietly in Chrome and writes down what you do as plain sentences: Type "Delhi" into the "From" field. Click the "Search" button.
Afterwards you read that list, fix anything odd, and tick the fields that are different each time (destination, date, passenger name). From then on the automation does the task and asks you only for those values.
flow-recorder folder somewhere permanent.chrome://extensions, switch on Developer mode, click Load unpacked, choose the folder.Portal — bus booking, 1 passenger. Press ● Start recording. The page reloads once.Clicks, typing, dropdowns, tick boxes, radio buttons, autocomplete pickers (type + arrow keys + Enter), keyboard shortcuts, hover menus, right-clicks, drag and drop, file uploads (the file name only), forms inside embedded boxes, new tabs, and page changes. For each step: the page, the element and every way to find it, and a screenshot with sensitive fields blurred.
Passwords, OTPs, card numbers, CVV, phone numbers, passport, PAN, Aadhaar, account numbers. These show as “Type a secret into …”. Payment pages from a bank or payment company are not captured at all.
The review page lists what you did as numbered sentences. Read it top to bottom once. For each step you can:
| Control | What it does |
|---|---|
| value | Change the recorded text. |
| changes every run | Tick this for anything that differs each time (destination, date, name). Give it a short name. The automation asks for it instead of reusing the recorded value. These appear in the orange list at the top. |
| ask me before this | On a click. The automation pauses here and waits for your OK. Use it on the final Pay / Book / Submit button. |
| Add note | A hint on one step, for you or for whoever builds the automation. |
| Remove | Drop a step that was a mistake. Nothing is lost; Restore brings it back. |
| screenshot | See the page at that moment. Download image to check or edit it. Remove screenshot deletes the image everywhere; the step stays. |
Above the steps there is a box for a note about the whole recording (optional): what it is for, anything the team should know.
Small mechanical steps (clicking into a field before typing, Tab, the page loading after a click) are hidden. Tick show small steps to see them. technical details shows how each element is identified.
If you are connected to the hub, every recording you stop appears here for the whole team automatically, and edits follow within seconds. Nobody has to send files around.
The Download menu on a recording gives:
Two ways. The first needs Node.js on the computer; the second is a script that is built from the recording.
cd flow-recorder/runner && npm install # once node run.mjs recording.json --login # first time on a site: sign in once; it stays signed in node run.mjs recording.json --destination Agra --travel_date 2026-10-14
Anything you leave out is asked at the prompt. The runner stops at every step marked ask me before this, leaves the browser open when done so you can check, and if something goes wrong leaves it open at that step so you can see what happened.
--dry-run prints the steps in plain English without opening a browser.
Show automation script on the review page gives a standalone script with the plain-English step written above every line, so you can check it matches what you did.
No. The extension only watches. It never clicks, types, or changes a page. It does not slow the site. While recording, the only things you see are the red pill and, if screenshots are on, a split-second capture at each step. When you are not recording, it does nothing at all.
Bookings made while recording are real bookings. The recorder does not stop or alter them; it just writes them down.
The page must be a normal website (http or https). Chrome's own pages and the new-tab page cannot be recorded. Reload the page once; if still nothing, on chrome://extensions press the refresh arrow on the Flow Recorder card.
Remove it, or record the task again. Recording the same task twice is useful anyway: Site health compares the runs and flags any field the site identifies differently each time, before an automation breaks on it.
Click the date as usual. It is recorded as clicks. For a date that changes every run, leave a note on that step; the automation needs a small adjustment there.
Record with one passenger first. Repeating sections are handled when the automation is built.
Everyone on the hub sees all recordings and can review and download them. You can delete only your own; admins can delete anything and manage members. Each person has their own access key; treat it like a password.