n8n - Browser Use
Skip to main content
Use the official n8n-nodes-browser-use-cloud community node. New nodes default to API V4. If your n8n instance cannot install community nodes, use HTTP Request nodes instead.

​
1. Install the node

  1. In n8n, open Settings → Community Nodes.
  2. Install n8n-nodes-browser-use-cloud.
  3. Restart n8n if it asks you to.
Do not install n8n-nodes-browser-use. That is an older third-party package.

​
2. Add your key

  1. Create a Browser Use API key at cloud.browser-use.com/settings.
  2. In n8n, create a Browser Use API credential.
  3. Paste the key.
  4. Leave the Base URL at its default value. The node picks the right API path from the API Version field.

​
3. Run your first task

  1. Add a trigger.
  2. Add the Browser Use node.
  3. Pick v4, Run, then Run and Wait.
  4. Add a task such as: Open browser-use.com and return the first three customer names shown on the home page.
  5. Run the workflow.
The node waits for the run and returns the result, status, cost, session ID, and events URL. Turn on Extract Structured Data when the next n8n node needs JSON.

​
Pick an API version

Existing workflows keep the version they were saved with. Updating the package does not move an old workflow to V4.

​
Common fixes

I only see the old task actions. Update n8n-nodes-browser-use-cloud, then add a new Browser Use node. New nodes use type version 2 and start on API V4. My key fails. Make sure the credential uses X-Browser-Use-API-Key and leave the Base URL unchanged. The run takes a while. Use Run and Wait and raise Wait Timeout. Set Max Cost USD when you want a hard spend limit.

​
Without the community node

Call the V4 API with plain HTTP Request nodes.
  1. Create a Header Auth credential with Name X-Browser-Use-API-Key and Value YOUR_API_KEY (without a Bearer prefix).
  2. Add an HTTP Request node named Create run: POST https://api.browser-use.com/api/v4/runs with that credential and JSON body {"task": "Find the top 3 trending repos on GitHub today"}. It returns the run id.
  3. Poll GET https://api.browser-use.com/api/v4/runs/{{ $('Create run').item.json.id }}/status with an If node and a Wait node (5–10 seconds) until status is completed, failed, or cancelled.
  4. Fetch GET https://api.browser-use.com/api/v4/runs/{{ $('Create run').item.json.id }} once. Branch on status: only a completed run has the answer in result (and in output when you sent an outputSchema); for failed or cancelled, read error.
V4 runs do not send webhooks, so poll the status endpoint. See polling guidance.
The HTTP pattern works with any workflow tool that supports HTTP requests: Make, Zapier, Pipedream, or custom orchestrators.

​
Sources