Recording a workflow
Build a workflow by doing the task once by hand and letting the recorder write the blocks.
What the recorder does
Press Record, work through the task in a real browser profile, and the blocks appear on the canvas as you go. It is the fastest way to get a first draft of a workflow, and it means you do not need to know a CSS selector to automate something.
What it records is intent, not raw events. Typing a name into a field becomes one block carrying the finished text, not forty keystrokes. Clicking a link that navigates becomes one click block, because the navigation follows from the click when the workflow replays.
Recording a session
- Start a profile, then open a workflow in the RPA editor.
- Press Record and pick the running browser tab you want to record.
- Do the task. A banner over the canvas shows the step count and lets you pause or undo.
- Press Stop. The blocks are already wired in order on the canvas.
- Save, then run it against a profile to check it replays.
The first block is a Navigate step for whatever page you started on, so the workflow opens the right page instead of assuming the browser is already there.
Options
- Mask passwords — password fields are recorded as a variable rather than plaintext. Leave this on: workflows sync to the server and can be shared, and a plaintext password would go with them.
- Record scrolling — captures scroll positions. Useful on infinite feeds, noise on ordinary forms.
- Record pauses as delays — turns your own thinking time into delay blocks, for sites that dislike instant input.
Cleaning up the recording
A recording is a draft. Expect to delete a few stray clicks, and to check any block flagged with a warning — that mark means the recorder could not find a selector it was confident was unique, and the block may need a better one before it will survive a page redesign.
Every save keeps a version, so you can experiment with a recorded draft and restore the previous state if the edit makes things worse.