← All posts

Automating repetitive browser work without code (and when not to)

A lot of account work is the same few clicks repeated across many browsers: open a dashboard, check a number, paste it somewhere, move on. Automation flows let profiles do those steps by themselves — without writing code — and they are just as useful for knowing when not to automate.

What a flow is

A flow is a list of steps a person would do in a browser: open an address, click, type, choose from a list, scroll, wait, take a screenshot. Steps can use variables, repeat, branch (if the page shows "Welcome" … otherwise …) and collect data into a results table. You run a flow on one profile or on many at once, by hand or on a schedule.

Three ways to start

  1. From a template. The cookie robot warms up a new profile by visiting popular sites like a person; Open a page and read it is a good first exercise.
  2. Record it. Open a Chrome profile, press Record and do the task once. Clicks, typing and scrolling become steps; passwords are never recorded. The recorded flow runs on Firefox profiles too.
  3. Import one from the template gallery, where shared flows appear after our team has reviewed them. Read the steps before you run someone else's flow.

Feed it data

Most repetitive work differs only in its data: a different search term, address or product per account. Attach an Excel, CSV or text file to the run and use its columns in steps as ${row.column}. Either each profile gets one row (profile 1 → row 1), or every profile goes through all rows.

Connect it to the rest of your work

  • Google Sheets: add a row to a sheet or read rows from it, using a service account from your own Google Cloud project. Share the sheet with that account's e-mail.
  • Ask AI: send a question (with variables, such as the text a step just read) to any OpenAI-compatible chat API — including one running on your own computer — with your own key. The answer goes into a variable for the next steps.
  • E-mail codes: wait for a message in a mailbox you added (IMAP) and put the code into a variable. Passwords for mailboxes come from the run's data file, never from the flow itself.
  • HTTP requests, a clipboard step, and save to a text file cover most of the rest.

Keys and mailbox passwords stay encrypted on your computer; flows only refer to them by name.

Run it safely

  • Concurrency: decide how many profiles run at the same time; more is faster but uses more memory.
  • Results and logs: every run keeps its log, screenshots and results; failed profiles can be retried in one click.
  • Schedules run on your computer while the app is open (in the background is fine): once, daily, weekly, every few minutes, or by a cron rule.

When not to automate

Automation is for your routine work on accounts you're allowed to manage. Many platforms don't allow automated posting, liking, following or messaging. If a platform's terms don't allow a task to be automated, do it by hand — no tool makes a forbidden action acceptable. And never use flows to solve CAPTCHAs or get around a site's protections.

Get started

Open Automation → New flow, start from the cookie-robot template, run it on one profile and read the log. Then replace one step at a time with your own.