Flow.Documentation
New in 0.7.21

RPA screenshots

See what the browser saw, right where you follow the run.

Operating a website with browser steps (RPA)

When a workflow operates a website with browser steps (RPA), every step can take a screenshot. You see them where you follow the run: in the workflow editor, in the run panel of a dashboard button, on the home and under the answer of an AI Colleague in the chat. Only someone who may see that run sees them.

In short

  • A filmstrip per run

    Screenshots per browser step in the editor, with the step that took it, the time, zoom, and previous and next.

  • Live while it runs

    A dashboard button or row action shows the screenshots in its run panel as they arrive.

  • In the chat

    When an AI Colleague's workflow takes screenshots, they appear under the answer, ready to open large.

  • Off until you switch it on

    The builder decides per browser step whether the person who starts it may see its screenshots.

  • Only your own run

    You see the screenshots of a run you may read, never through an open link and never another employee's run.

  • Every view on record

    Each view of a screenshot is in the audit log, and a risky setting shows up in the security overview.

What you can do

What you can do

  1. Let a workflow operate a website

    Add a browser session, say which site it may visit, and let it fill in fields, click and read tables the way a person would.

  2. Follow the run in the editor

    Run the workflow and look at the filmstrip: every screenshot with the step that took it. That is how you see what went wrong, without guessing.

  3. Show the screenshots to the person who starts it

    Switch on showing screenshots to the person who starts it for a browser step, and a colleague who presses the button on a dashboard follows along.

  4. Screenshots under an AI Colleague's answer

    Give an AI Colleague a workflow with browser steps as a tool, and the screenshots appear in the conversation while the tool runs.

The guides

The guides

Advanced

Operating a website with browser steps (RPA)

Not every system has an API. A supplier portal where you look up invoices every week, Flow can operate like a person too: fill in, click, read a table. You build a browser session on a demo portal (if operating websites is still off, you switch it on at the step itself) and look at the screenshots Flow keeps with the run.

10 steps± 7 minVideoVerified 22 Oct 2026
Beginner

Runs and problems

Everyone makes a typo now and then. Flow helps you find it: Problems lists what is already wrong right now, and Runs tells you for every run what went in, what came out and where it went wrong. You build a small workflow with a mistake in it on purpose, see it fail, find out why and fix it.

9 steps± 6 minVideoVerified 22 Oct 2026
Professional

Buttons that run workflows

A dashboard is not only for looking. A button starts a workflow: enter an order, make a report, fetch data again. The button can ask a few questions first and ask for confirmation; then you watch the run happen live and the tiles refresh. A table can have an action on every row, with that row as input.

8 steps± 6 minVideoVerified 22 Oct 2026
Professional

Agent tool: workflow

An agent can start a workflow itself when it needs to look something up or do something. You choose which workflows it may use, say when, whether the workflow only reads or changes something, and how often per run. A workflow that changes something is only offered once the agent may change data.

4 steps± 3 minVideoVerified 22 Oct 2026

More that is new