You define the route
The flow follows its recorded actions. Add if/else decisions and error paths when your task needs different outcomes.
Run your tested browser steps with new inputs. Get structured results without AI deciding what to do at each step.
Saved pagination rule
From collecting market data and scraping leads to gathering research, turn web data into sales opportunities and better-informed decisions.
The flow follows its recorded actions. Add if/else decisions and error paths when your task needs different outcomes.
Use named fields and lists to turn information on a page into structured data your next step can use.
Run your published flows from Make, n8n, ChatGPT, Claude or your own application through API and MCP. Provide inputs, start runs and use the results in your next step.
Run your flow with example inputs and check that the output is right.
Call the published endpoint from your application or automation platform.
Check the run status, retrieve the output and pass the data to the next task.
No. Ordinary successful runs follow recorded steps without AI requests. AI repair is a separate option for supported selection failures.
Yes. Configure how the list should handle no results, including an optional no-results message. You can also branch based on whether collected data is empty.
A run can fail if it can no longer find a required element. Configure block solvers, error paths or AI repair to decide how the flow handles that situation.
ChatGPT and Claude can find your enabled flows, provide inputs, start runs, check their status and retrieve results through MCP. Browserflow executes the tested browser steps, so each run follows the workflow you recorded. Explore AI connections.
A helping hand when a website changes.
Use new inputs to collect leads, gather market data or run your next sales process.