RPA (Automation)

Build a process once — a sequence of steps, visually, no code — then run it on any profile. It drives the exact same isolated, fingerprinted browser a normal launch would, so it's indistinguishable from you clicking it by hand.

Building a process

Open Processes → New Process, name it, and add steps from the command palette one at a time. Steps run top to bottom; if and loop can nest other steps (including more if/loop) inside themselves.

CSS & XPath selectors

Anywhere a command takes a selector, you can use either a normal CSS selector or an XPath expression — XPath is auto-detected from its shape, no prefix needed:

This means you can paste DevTools' "Copy XPath" output directly into any selector field with no changes.

Command reference

Using loop variables — ${...}

forElements, forData, and whileLoop are only useful if body steps can act on the current item — so any selector, text, URL, or value field elsewhere in the process can reference a captured variable with ${variableName}, substituted fresh on every iteration. This works with any variable — one set by extractText/extractAttribute/evaluate earlier in the process too, not just a loop's own index/item variable.

{ "type": "forData", "items": ["alice@example.com", "bob@example.com"],
  "itemVariable": "email",
  "body": [
    { "type": "type", "selector": "#email", "text": "${email}" },
    { "type": "click", "selector": "#submit" }
  ]
}

Conditions (if / whileLoop)

Data Processing

Pure variable transforms — no page interaction. Useful for reshaping whatever you extracted before branching on it.

Profile Information

Writes back to the profile the process is running against — handy for recording an outcome that a later run (or you) can see in the Profiles grid.

Google Sheets

The Google Sheet action reads a sheet into a variable, writes rows back, or clears a range — so a process can pull its input data from a spreadsheet and log its results to one. Combined with For Loop Data, that's the usual "run this once per row" pattern.

One-time setup

Access uses a Google service account — a robot Google account you create and share sheets with.

1. In the Google Cloud console, create (or pick) a project and enable the Google Sheets API.
2. Go to Credentials → Create credentials → Service account and create one.
3. Open the new service account → Keys → Add key → Create new key → JSON. A .json file downloads.
4. In Parallel, open ⚙ Settings → Google Sheets, paste the entire contents of that file, and click Connect. Parallel verifies the key immediately.
5. Settings then shows the service account's email address. Open any spreadsheet you want to use, click Share, and share it with that address — Viewer is enough to read, Editor is required to write or clear.

Fields

Example: run a process once per row

Read a sheet of accounts, loop over the rows, and append a result line for each — the shape most Sheets-driven automations take.

1. Google Sheet — Read
     Spreadsheet ID: 1AbC…                Worksheet: Accounts
     ☑ The first line is set to key       Save to: rows

2. Run JavaScript
     Script: JSON.parse(vars).map(r => r.email).join('\n')
     (turn the JSON into one email per line for the loop below)

3. For Loop Data — items: the emails, itemVariable: email
     └─ Go to URL:  https://example.com/login
     └─ Type:       selector #email, text ${email}
     └─ Google Sheet — Write
          Worksheet: Results   ☑ Append
          Values:    ${email},done

Process settings

Running & debugging

Click Debug in the process editor's header — a popup lets you pick which profile to run it on, then launches (or reuses an already-running) profile and executes the process against it.

Every run is recorded in that process's Debug logs — the last 20 runs per process, showing the full step tree exactly as it executed, including which nested steps inside an if or loop ran and whether each one succeeded or failed. Screenshots taken mid-run appear inline.

Import / export

Export a process to JSON to share it, back it up, or version it outside the app. Import accepts pasted JSON with a choice of Append (add to your existing processes) or Replace (overwrite). Since a hand-pasted or scripted import bypasses the editor's own UI limits, the same 10,000-loop cap is enforced when the process actually runs, not just when you build it in the editor.

Signed in, processes sync to your account the same way profiles do — build one on one machine, sign in elsewhere, and it's already there.