Skip to content

The 5-tab problem: let your browser do the copy-paste

One small job, five tabs: a competitor's price, a second shop, a spreadsheet, a chat assistant and your inbox. Here is why that adds up, and how one workflow in your browser does it for you.

Dannick K.
October 13, 2026 · 2 min read
PresentBoard

Also in Français

The price-watch workflow drawn node by node, beside the post title.
Share
On this page
  1. The 5-tab problem
  2. Let the browser do it
  3. Try it

The 5-tab problem

Count the tabs you need for one small job. To check a competitor’s price you open their shop, then a second shop, then your spreadsheet, then a chat assistant to compare, then your inbox to tell the team. That is five tabs for one job.

The pattern

You open five tabs to do one job.

One job. That is the whole idea of a workflow.A workflow chains those steps so each one passes its output to the next.

Kinetic line
Text version
  1. The pattern: You open five tabs to do one job.

Each of those tabs is really a step. Put the steps in order and you have a workflow.

Your five tabsOne workflow
The shop page
Trigger: the page loads
Hunting for the price
AI step: read the price
The spreadsheet
Rule: did it drop?
Your inbox
Notify me

Your inbox becomes a notification.A notify node sends the result to your phone.

Analogy split
Text version
  1. Your five tabs: The shop page ≈ One workflow: Trigger: the page loads
  2. Your five tabs: Hunting for the price ≈ One workflow: AI step: read the price
  3. Your five tabs: The spreadsheet ≈ One workflow: Rule: did it drop?
  4. Your five tabs: Your inbox ≈ One workflow: Notify me

It adds up quickly. Here is what one morning habit costs in a week:

One price check, per week

3h 12m

Five competitor pages, checked by hand every morning. Example figures

Opening tabs38 min
Finding prices61 min
Copying to a sheet54 min
Comparing39 min

Where it goes: most of it is finding and copying.Finding and copying are the steps an AI extract node and a sheet node replace.

Stat counter
Text version
  1. One price check, per week: 3h 12m
  2. Opening tabs: 38 min
  3. Finding prices: 61 min
  4. Copying to a sheet: 54 min
  5. Comparing: 39 min

Price checks are only one example. These five browser tasks follow the same pattern:

From the post

5 browser tasks AI can take over

  • Summarise long pages (done)automated
  • Pull prices and names into a sheet (done)automated
  • Fill the same form again and again (done)automated
  • Watch a page for changes (done)automated
  • Collect images from a page (done)automated

Collecting images.Scraping: a node collects the image URLs from the page and downloads them.

Checklist
Text version
  1. 5 browser tasks AI can take over
  2. Summarise long pages
  3. Pull prices and names into a sheet
  4. Fill the same form again and again
  5. Watch a page for changes
  6. Collect images from a page

Let the browser do it

Here is the price check as one workflow. It starts on its own, and each step passes its result to the next.

Price On Page Watch

TriggerWhen the price changes
DataRead the price
CoreRead last price
LogicDid the price drop?
price changed on the page
price: €389
last price: €449
dropped: yes (−13%)
+2 more stepsExample figures

Run it. Every step shows what it produced.Run: each node's output is shown on the canvas; the last steps alert you and store the price.

Live flow
Text version
  1. price-on-page-watch.awf
  2. price changed on the page
  3. price: €389
  4. last price: €449
  5. dropped: yes (−13%)

It starts on its own

The trigger fires when the price on the page you watch changes. You do not schedule anything or press a button.

It reads the page

The workflow reads the price on the page the way you would, and keeps it as clean data.

It remembers

It compares the new price with the last one it saw, so you only hear about real changes.

A simple rule decides

If the price fell, the workflow continues. Otherwise it stops quietly.

Every step shows its result

When it runs, you can see what each step produced. That makes it easy to check, and to fix.

Building it takes a few actions, all on the same screen. Each mark shows where it happens.

The lesson’s workflow, My first workflow, on the canvas: a sticky note, then When Started, Get Selected Text and Edit Fields joined by lines. The header has the active switch and Save; Test Workflow is above the canvas on the right.The lesson’s workflow, My first workflow, on the canvas: a sticky note, then When Started, Get Selected Text and Edit Fields joined by lines. The header has the active switch and Save; Test Workflow is above the canvas on the right.

Three actions, one screen.Three nodes configured on one canvas, with no code.

Guided screenshot
Text version
  1. 1. Read from the page: Pick what to read.
  2. 2. Shape the data: Keep only what you need.
  3. 3. Run it: Watch each step light up.

It runs on the real page, in your own browser, while you are signed in to your own accounts.

shop.example.com/barista-pro

Home · Coffee · MachinesBarista Pro espresso machine★★★★☆ · 1,204 reviews€389€449Add to cart
Price watchRunning
  • Page loadedshop.example.com
  • Price found€389 (was €449)
  • Dropped 13%above your 10% rule
  • Notification sentto your phone

It runs on the page. Every step shows up in the log.A content script reads the DOM; the run log streams each node's result.

Fake browser
Text version
  1. shop.example.com/barista-pro: Barista Pro espresso machine · €389
  2. Price watch
  3. Page loaded: shop.example.com · Price found: €389 (was €449) · Dropped 13%: above your 10% rule · Notification sent: to your phone

There is one more difference, and it matters for privacy.

Your browser
Someone else's server
Your browsersigned in as you
Cloud automationa typical tool
your login + page data
the result
NetworknoneYour data leavesno

AWFlow runs inside your browser, so nothing has to leave.Local execution reuses your browser session; no data leaves the device.

Round trip
Text version
  1. Your browser: Your browser · Someone else's server: Cloud automation
  2. Your browser → Cloud automation: your login + page data
  3. Cloud automation → Your browser: the result
  4. Round trip: ≈ 2 s · Your data leaves: yes
  5. Cloud automation → Your browser · Network: none · Your data leaves: no

Two places a workflow can run

Most automation tools run on their own servers. AWFlow runs in your browser.

A cloud tool needs your keys

To work on a site for you, a server needs your login and a copy of the page.

It sends the result back

That works, and it is fast. Each run is still a round trip through someone else’s computer.

Your data took a trip

Your session, the page content and the result all passed through a server you do not control.

Or it stays with you

When the workflow runs inside your browser, it uses the session you already have. Nothing leaves.

Drag the handle to compare the two mornings.

Before

The manual way

  • Shop A
  • Shop B
  • Sheet
  • Chat
  • Inbox

47 min

Every morning, by hand.

After

With one workflow

  • Watch
  • Extract
  • Notify

40 s

Runs while you do something else.

Drag the line to compare the two mornings.The slider compares both states; it works with the keyboard too.

Before / after
Text version
  1. Before: The manual way, 47 min. Every morning, by hand.
  2. After: With one workflow, 40 s. Runs while you do something else.
  3. Compare before and after

What about you? Pick one to see how other readers answered.

Quick poll

Which browser chore eats most of your day?

Example results

Reveal. Copying between tabs wins. (Example results.)Example results, labelled on screen: there is no poll backend.

Poll
Text version
  1. Which browser chore eats most of your day?
  2. Copying data between tabs: 41% · Filling the same forms: 23% · Checking pages for changes: 21% · Summarising long reads: 15%

Try it

You can copy the whole workflow and change the shop link for your own.

Your turn

Steal this workflow

Open it in AWFlow, point it at the shop page you watch, and it runs in your browser.

Open in AWFlow (opens in a new tab)docs.awflow.io/examples/price-on-page-watch.awf
Scan to open

Call to action. Viewers scan the code, readers click the link.The link opens the docs example in AWFlow's import page; the QR code encodes the same link.

Try it
Text version
  1. Steal this workflow · Open it in AWFlow, point it at the shop page you watch, and it runs in your browser. · https://docs.awflow.io/examples/price-on-page-watch.awf

What we covered

  1. One job, five tabs
  2. One workflow does the clicks
  3. It runs in your browser

Three. It stays in your browser.Chapter 3: local execution; data stays on the device.

Recap
Text version
  1. What we covered
  2. One job, five tabs
  3. One workflow does the clicks
  4. It runs in your browser

Automate the web you're on. Free, in your browser.