Skip to content

BrowserZap 0.5 is out on npm for Windows · Chrome Web Store listing in review · Get started

BrowserZap

Docs

Workflows

A workflow is a saved task: its steps, the sites it may act on, and {{parameters}} for what changes each time. Replaying one runs every step through the same checks as a live call: exact targets, approvals, sensitive fields, site limits.

Record one

By doing it yourself

  1. Open the page to start from and press Record in the side panel.
  2. Do the task once. Your own clicks, typing, choices and Enter presses become steps.
  3. Review the steps (remove any you do not want), name the workflow and save.

What you type becomes a parameter, not a stored value. What you type into a password or other sensitive field is never recorded: on every run, you type it yourself.

Through your agent

workflow_record with action: "start" and a name, let the agent do the task, then action: "stop". Only steps that succeeded are kept.

Replay it

  • Side panel: open the workflow, fill in its values, press Run. No agent needed.
  • Your agent: workflow_run with params.
  • Terminal: browserzap run <workflow> --params row.csv runs it with no agent; the exit code is 0 when every run completed.

A run stops at the first step it cannot verify and says which one and how to continue (startAt). A step that needs approval waits for you; a password or CAPTCHA is handed to you, then the run can continue.

Built for slow and fickle sites

  • Each step waits for its target and lets the page settle first.
  • A step can carry a pause you choose (waitBeforeMs), for a site you know is slow.
  • The site's own error page is recognised (SITE_ERROR), never mistaken for success.
  • A step that can clear up is retried from the step that opened it (for example reopening a dialog that closed), never by repeating a submit, payment or deletion.
  • Optional steps (dismiss a banner) can be marked onFail: "skip".

Many rows, unattended (Pro)

One workflow over many rows: paste a CSV or list in the side panel (Run for many), or pass paramSets. A failed row is reported with its step and cause and the next one runs; at the end you get a report of what needs attention and can re-run only the rows that did not complete. background: true returns at once and workflow_status follows it.

Where workflows live

In BrowserZap's folder on your computer, as plain files. They never contain element references, approval ids or sensitive values. Plans and limits for workflows are being set as Pro launches; see pricing.