Import recordings into editable drafts

Recordings captured with the Chrome extension (or the desktop app) become useful once you import them: the import creates a draft automation whose steps you can edit, reorder, parameterize, and mix with app integrations.

From recording to draft

When you import a recording, each captured interaction becomes an editable browser step — navigate, click, type, press, select, scroll, scrape, scrapeList, wait, or screenshot. Every step keeps the full ranked selector list and element fingerprint from the recording, so nothing is lost in the conversion.

Import a recording

1. In the web app, open your recordings and choose the one to import.
2. Tyrbo creates a draft automation from it and opens the editor.
3. The draft is yours to change — the original recording stays untouched, so you can import it again for a different automation.

If you recorded with the desktop app, imports work the same way; recordings made on a linked device show up in the same place.

Edit the steps

In the step editor you can:

• Rename, reorder, and delete steps. Recordings often include a stray click or a scroll you don't need.
• Edit typed values. Replace literal text you typed during recording with variables using the {{variable}} syntax — for example, type a customer name from a trigger payload instead of the one you used while recording.
• Tune per-step options: a timeout, retry count, whether the step is optional (the run continues if the element never appears), and an extra wait after the step for slow pages.
• Inspect selectors. Each step shows its candidate selectors; if you know a page well you can adjust which selector leads.

Combine with integrations, loops, and branches

Browser steps and app-integration steps live in the same workflow. Common patterns:

• Scrape, then send: a scrapeList step feeds a loop that writes each item to a spreadsheet or CRM via an integration step.
• Trigger, then act in the browser: an app event (like a new email) triggers the flow, and browser steps enter the data into a site with no API.
• Branch on scraped values: route the flow differently depending on what a scrape step found.

Adjacent browser steps run together in one browser session during a run, so a logged-in state carries through a sequence of browser steps without extra work.

Sessions and logins

If the recording included a session export, the draft's browser steps replay against that saved session in the cloud. If the site requires your local machine (device-bound login, MFA), mark the browser steps to execute locally and they'll run through the desktop app instead — see Cloud runs vs local runs.

Save and run

Save the draft, run it once manually, and watch the per-step results. Once it behaves, add a schedule or trigger. If a step fails or gets flaky, the run's screenshots and snapshots show you exactly where — see Troubleshooting flaky selectors.