# Turn a repeated browser task into an SOP and automation

> Capture a repetitive browser workflow, document it, identify fragile steps, and automate the stable parts.

- Canonical: https://gptnavi.com/workflows/browser-task-to-sop-and-automation
- Category: Operations
- Difficulty: Intermediate
- Setup time: 90 minutes
- Estimated time saved: 2-8 hours
- Last materially updated: 2026-08-24
- Best for: Operators, Agency teams, Support teams, AI consultants
- Tools: Scribe, Tango, Bardeen, Make, Notion

## Quick answer

This workflow helps teams move from undocumented click work to a maintained SOP, then automate only the parts that are safe and repeatable.

## When to use it

- Client onboarding
- CRM updates
- Marketplace operations
- Internal admin tasks

## Steps

1. **Record the task** — Run the task once while capturing each click, input, decision, and required source. Tool: Scribe. Expected output: A first draft step-by-step guide.
2. **Clean the walkthrough** — Edit labels, remove irrelevant clicks, add screenshots, and note judgment calls. Tool: Tango. Expected output: A readable SOP draft.
3. **Separate stable from risky steps** — Mark which steps are rule-based, which need human review, and which depend on changing page layouts. Tool: Notion. Expected output: An automation readiness checklist.
4. **Automate the safe clicks** — Create a browser automation for copy, paste, lookup, scraping, or routing steps that do not require judgment. Tool: Bardeen. Expected output: A lightweight browser automation.
5. **Connect the workflow** — Send outputs to a database, CRM, Slack, email, or task tracker. Tool: Make. Expected output: A repeatable SOP with partial automation.

## Prompt templates

### SOP risk reviewer

Review this SOP and mark which steps are safe to automate, which require human review, and which are fragile because of changing UI or missing data. SOP: [paste]

### Automation brief

Turn this SOP into an automation brief. Include trigger, inputs, steps, output, exceptions, review points, and tools to connect. SOP: [paste]

## Common mistakes

- Automating before the manual process is stable
- Ignoring login and permission issues
- Not documenting what humans still need to review

## Related workflows

- https://gptnavi.com/workflows/screen-recordings-to-sops-and-training-docs
- https://gptnavi.com/workflows/small-team-ai-adoption-playbook
- https://gptnavi.com/workflows/monitor-competitor-pricing-and-product-pages