Browserflow Documentation
Browserflow is built to be plug-and-play. In Make.com or n8n you select the Browserflow module/node, connect your API key once, choose your workflow from a list, pass input values, and use the output directly in the rest of your automation.
Plug & Play in Make.com and n8n
Most teams should start here. You do not need to build manual API requests for day-to-day use. The Browserflow module/node handles connection, workflow selection, input mapping, and output handoff in one flow:
- Step 1: add the Browserflow module/node to your Make.com or n8n scenario.
- Step 2: connect once using your Browserflow API key.
- Step 3: select the workflow you already tested in Browserflow.
- Step 4: map module inputs to your upstream data.
- Step 5: map returned outputs to the next module and run end-to-end.
Quickstart Guide
From new account to live workflow:
- Create account and sign in: make sure your trial/subscription is active.
- Create or clone a flow: generate with AI or clone from the community templates.
- Define inputs and outputs: confirm the schema before running.
- Run one test in Browserflow: validate run quality and returned output variables.
- Open Make.com or n8n: add the Browserflow module/node.
- Connect API key: one-time connection in the module settings.
- Pick your tested workflow: choose it from the built-in workflow dropdown.
- Map module inputs: pass dynamic values from previous steps.
- Map outputs downstream: connect returned values to the next app/module and run a full scenario test.
AI Generates Your Web Automation
You describe what you want, and AI generates the web automation for you. You can then run, improve, and reuse that workflow across campaigns and clients.
- Prompt your goal: for example lead scraping, enrichment, or growth workflows.
- Review generated flow: check inputs, outputs, and run quality.
- Go live fast: connect it in Make.com and n8n without custom coding.
Create Your Flow
You can create flows in two ways:
- Generate with AI: explain the task and let Browserflow build the automation.
- Clone from community: copy a proven flow and adjust it to your use case.
Choose Workflow from the List
In Make.com and n8n, once your key is connected, Browserflow shows your workflows in a selectable list. Pick the one you want, map fields, and run.
- No manual endpoint lookup: choose from your workflow list.
- Easy switching: swap workflow without rebuilding the whole scenario.
- Reusable setup: keep the same input/output mapping pattern across workflows.
Inputs
Pass input values directly from previous modules, like form submissions, CRM rows, sheet rows, or webhook payloads.
{
"input_values": {
"task": "Visit Booking.com, search hotels in Paris for next weekend, sort on the best-rated options descending and return the first 10 items",
"city": "Paris",
"date_range": "next_weekend",
"guests": 2,
"currency": "EUR",
"limit": 10
}
}
Results You Get Back
Browserflow returns structured output every run. You get items and an output_variables list so mappings stay stable and easy to reuse.
{
"status": "success",
"items": [
{
"key": "hotels_top_10",
"value": [
{ "rank": 1, "hotel_name": "Hotel Le Six", "rating": 9.3, "price_per_night_eur": 312 },
{ "rank": 2, "hotel_name": "Le Narcisse Blanc", "rating": 9.2, "price_per_night_eur": 428 },
{ "rank": 3, "hotel_name": "Hotel D'Aubusson", "rating": 9.2, "price_per_night_eur": 510 },
{ "rank": 4, "hotel_name": "Relais Christine", "rating": 9.1, "price_per_night_eur": 475 },
{ "rank": 5, "hotel_name": "Hotel Monge", "rating": 9.1, "price_per_night_eur": 289 },
{ "rank": 6, "hotel_name": "Hotel Le Bristol Paris", "rating": 9.0, "price_per_night_eur": 980 },
{ "rank": 7, "hotel_name": "Hotel Fabric", "rating": 9.0, "price_per_night_eur": 244 },
{ "rank": 8, "hotel_name": "Hôtel des Grands Boulevards", "rating": 8.9, "price_per_night_eur": 266 },
{ "rank": 9, "hotel_name": "Hotel Alfred Sommier", "rating": 8.9, "price_per_night_eur": 355 },
{ "rank": 10, "hotel_name": "Le 123 Sebastopol", "rating": 8.8, "price_per_night_eur": 238 }
]
},
{
"key": "run_summary",
"value": {
"city": "Paris",
"date_range": "next_weekend",
"sorted_by": "rating_desc",
"returned_items": 10
}
}
],
"logs_ref": "logs/endpoint/paris-hotels-weekend/uuid",
"artifacts": [
{ "type": "screenshot", "name": "booking_search_results.png" }
],
"timing": {
"start": "2026-04-17T09:58:11+00:00",
"end": "2026-04-17T09:58:39+00:00"
}
}
Output List Mapping Across Thousands of Apps
In Make.com and n8n, map Browserflow output fields into downstream steps like Google Sheets, Airtable, HubSpot, Slack, Notion, email tools, CRMs, ad tools, and thousands more apps.
- Use
output_variablesas your mapping reference. - Use returned
itemsas live run data. - Chain Browserflow output directly into next modules without custom code.
Session Viewer
Session Viewer helps you debug and validate runs. You can inspect logs, execution status, and what happened step by step before you publish to production.
Test Replay & Prompt Quality
Browserflow provides a built-in Test Replay feature allowing you to quickly validate how your workflow handles different variables without running full production loads.
- Test Edge Cases: Try passing extreme or empty input variables to see if the extraction stays stable.
- Improve Prompt Quality: If the output structure varies between tests, refine your flow's core prompt. Be explicit about expected formats (e.g. "always return 'Not Found' instead of empty arrays").
- AI Self-Healing: Browserflow uses intelligent recovery, but a solid base prompt significantly improves speed and reduces recovery time. Standardizing your prompt language leads to predictable JSON structures downstream.
Make & n8n Module Reference
This is the short reference for the Browserflow module/node fields, so you can configure it quickly without repeating the full quickstart steps.
- Connection: API key (connect once).
- Workflow: select from your saved Browserflow workflows.
- Inputs: dynamic input fields based on your workflow schema.
- Output: structured payload for direct mapping to downstream modules.
Browserflow Module/Node (reference)
Connection -> API Key
Workflow -> Select from list
Inputs -> Dynamic fields from schema
Output -> Map into next modules
Use this reference while configuring the module; use the Quickstart section above for the full first-run sequence.
Advanced API (Optional)
This section is for developers who want to create and reuse Browserflow automations directly in their own codebase/workspace. For most users, the Make.com/n8n module is faster.
Authentication Model
- Template management endpoints (
/flow-builder,/saved,/flows/{flow}/publish-endpoint): require authenticated session and active trial/subscription. - Public invoke/metadata endpoints (
/saved-flows/*,/endpoint/*): callable without app session for external integrations. - Browserflow module/node: handles connection setup for you via your API key.
Template API
GET /flow-builder: list your flow templates.POST /flow-builder: create a flow template.POST /saved/{flow}/replay: run a saved flow with new input.
POST /flow-builder
{
"name": "Lead Finder NL",
"template_id": "lead_finder_v1",
"prompt_goal": "Find local business leads with contact details",
"input_schema": [
{ "name": "query", "type": "string" },
{ "name": "max_results", "type": "number" }
],
"output_schema": [
{ "name": "company_name", "type": "string" },
{ "name": "website", "type": "string" },
{ "name": "email", "type": "string" }
],
"proxy_country": "nl",
"browser_profile_id": 7
}
201 Created
{
"message": "Flow template created.",
"data": {
"id": 123,
"name": "Lead Finder NL",
"template_id": "lead_finder_v1",
"input_schema": [...],
"output_schema": [...]
}
}
Publish & Reuse API
POST /flows/{flow}/publish-endpoint: publish/update endpoint name and return invoke URLs.POST /saved-flows/{user}/{endpointName}: invoke by exact endpoint name (no slug fallback).POST /endpoint/{endpointKey}/invoke: invoke by endpoint key.GET /saved-flows/{user}/{endpointName}/metadata: endpoint + schema metadata.GET /endpoint/{endpointKey}/metadata: metadata lookup by endpoint key.
Public endpoint routes require a user API key header. Use X-Browserflow-Api-Key (recommended), X-Api-Key, or Authorization: Bearer ....
POST /flows/123/publish-endpoint
{
"endpoint_name": "lead-finder-nl"
}
201 Created
{
"message": "Endpoint published.",
"data": {
"endpoint_name": "lead-finder-nl",
"endpoint_key": "uuid",
"invoke_url": ".../saved-flows/{user}/lead-finder-nl",
"metadata_url": ".../saved-flows/{user}/lead-finder-nl/metadata",
"invoke_by_key_url": ".../endpoint/{endpointKey}/invoke",
"metadata_by_key_url": ".../endpoint/{endpointKey}/metadata"
}
}
Invoke Input Rules
Invoke endpoints accept input from the first available container in this order: input, input_values, variables, inputs, payload. If none exist, top-level fields are used.
Optional helper fields: login_id, cookie_locker_id, browser_profile_id.
POST /saved-flows/42/lead-finder-nl
X-Browserflow-Api-Key: bfu_****************************
{
"input_values": {
"query": "plumber amsterdam",
"max_results": 25
}
}
200 OK
{
"status": "success",
"items": [
{ "key": "company_name", "value": ["Plumber Pro BV", "AquaFix Amsterdam"] },
{ "key": "website_url", "value": ["https://plumberpro.nl", "https://aquafix.nl"] }
],
"output": {
"company_name": ["Plumber Pro BV", "AquaFix Amsterdam"],
"website_url": ["https://plumberpro.nl", "https://aquafix.nl"]
},
"logs_ref": "logs/endpoint/lead-finder-nl/uuid",
"artifacts": [],
"timing": {
"start": "2026-04-17T08:12:45+00:00",
"end": "2026-04-17T08:12:45+00:00"
}
}
Metadata Output
Metadata responses include reusable integration details: method, content_type, input_schema, output_schema, input_variables, and output_variables.
Error Codes
- 401: missing/invalid API key on public endpoint routes.
- 403: not owner for protected auth routes.
- 402: active trial/subscription required on protected routes.
- 404: endpoint or flow not found.
- 422: validation failed (for example duplicate endpoint name or invalid payload fields).
- 429: rate limit exceeded (login/runtime/public endpoint routes).
Rate Limiting
Route-level throttling is enabled: login attempts, runtime preview/start, and public endpoint invoke/metadata are all rate-limited. Clients should still implement retries with backoff and queueing for burst traffic.
Marketplace & Community
Community is a core part of Browserflow. Clone ready-made web automations, share your own, and grow together.
- Clone flows for lead generation and growth hacking use cases.
- Share your own workflows and help others ship faster.
- Join discussions, feedback loops, and practical playbooks in the community.
- Build reputation by sharing automations that deliver real results.
Operations & Troubleshooting
- Workflow not showing in module list: save/publish it in Browserflow first, then refresh your module.
- Auth error in Make.com or n8n: reconnect API key and test the connection again.
- Input fields not mapping: check field names in your workflow input schema.
- Output missing in downstream app: inspect
itemsand remap the expected output variable. - Result quality not consistent: improve the AI-generated flow and test with real sample data.
Best Practices
- Keep workflows focused on one outcome per flow.
- Use clear input and output names to simplify mapping in Make.com and n8n.
- Use AI generation or community clones to move fast.
- Use AI generation for first draft, then refine with real runs.
- Reuse proven flows across clients, campaigns, and markets.
Useful URLs
- Home:
/ - Studio:
/app - Docs:
/docs - Marketplace:
/templates - Community:
/community