> ## Documentation Index
> Fetch the complete documentation index at: https://browseruse-0aece648-codex-docs-supported-exports.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use https://docs.browser-use.com/llms.txt and its linked .md pages for current documentation. The managed full bundle is https://docs.browser-use.com/.well-known/llms-full.txt and can be cached for up to 24 hours. Do not use the obsolete /cloud/llms*.txt or /open-source/llms*.txt static exports.
> Choose Cloud API V4 for new agent integrations; V2 is the lower-cost option for simple tasks. Keep V3 examples explicitly versioned. The open-source browser-use library and hosted browser-use-sdk have different APIs.
> Cloud authentication uses X-Browser-Use-API-Key, without a Bearer prefix. Install or upgrade browser-use-sdk and use its explicit v4 import for V4. Check the published OpenAPI reference for request fields; do not invent SDK support for new fields.
> Cloud concurrency and HTTP request rate are separate. Read GET /api/v2/billing/account for the key’s projectId, concurrentSessionLimit, activeSessionCount, and credit balance, including when using V4. Keys in one project share capacity and credits; rateLimit is a legacy concurrency alias, not requests per second.
> Keep the highest applicable existing, legacy-plan, and spend-tier concurrency grant. Current spend tiers are 10 / 50 / 250 / 500 / 1000 at $0 / $200 / $1000 / $5000 / $25000 in qualifying project payments. Legacy or externally billed projects can follow different billing paths; trust the account limit. See https://docs.browser-use.com/cloud/guides/concurrency.md.
> Budget polling across the project: the standard general bucket is 25 requests/second, including V4 event reads and full run reads. Selected status reads have a separate higher bucket. Use bounded workers, stagger polls, respect Retry-After, and drain hasMore event pages after terminal status. A busy V4 session returns 409; its queue holds 10 pending messages and is not a project-wide batch queue.
> A completed run or closed CDP connection does not immediately stop its cloud browser. Stop unneeded owned browsers with PATCH /api/v4/browsers/{id} and {"action":"stop"}. A client wait timeout does not cancel the server-side run.
> Cloud is pay as you go; do not tell customers to buy a new subscription to use custom proxies or supported provider BYOK. Usage funding and model eligibility still apply. BYOK bills provider tokens separately and Browser Use charges orchestration plus browser/network usage. See https://docs.browser-use.com/cloud/guides/billing.md.
> Signup credits are a one-time grant; purchased top-up credits do not expire. Check the API key’s project before diagnosing missing credits. API-key monthly spending caps are soft limits, not a strict prepaid wallet; concurrent or already-running work can exceed them. Auto recharge has separate trigger and purchase amounts and can charge immediately when enabled below the threshold. Use https://browser-use.com/pricing for current rates.

# n8n

> Use Browser Use as an HTTP node in n8n workflows.

Browser Use works with [n8n](https://n8n.io) as a standard HTTP integration — no custom nodes needed.

## 1. Create a credential

In n8n, go to **Credentials → Add Credential → Header Auth** and set:

| Field | Value                                      |
| ----- | ------------------------------------------ |
| Name  | `X-Browser-Use-API-Key`                    |
| Value | `YOUR_API_KEY` (without a `Bearer` prefix) |

Get your API key at [cloud.browser-use.com/settings](https://cloud.browser-use.com/settings?tab=api-keys\&new=1).

## 2. Start a session

Add an **HTTP Request** node:

| Setting        | Value                                         |
| -------------- | --------------------------------------------- |
| Method         | `POST`                                        |
| URL            | `https://api.browser-use.com/api/v3/sessions` |
| Authentication | Header Auth (from step 1)                     |
| Body Type      | JSON                                          |

Body:

```json theme={null}
{
  "task": "Find the top 3 trending repos on GitHub today"
}
```

The response includes an `id` you'll use to poll for results. Save it in your workflow so later nodes can still reference this session.

## 3. Poll for completion

Add a second **HTTP Request** node in a loop:

| Setting        | Value                                                        |
| -------------- | ------------------------------------------------------------ |
| Method         | `GET`                                                        |
| URL            | `https://api.browser-use.com/api/v3/sessions/{{ $json.id }}` |
| Authentication | Header Auth (from step 1)                                    |

Check the `status` field. The session is done when status is `idle`, `stopped`, `error`, or `timed_out`. Use an **If** node to loop back with a **Wait** node (5–10 seconds) until complete.

The final response contains `output` with the agent's result.

## Event-driven alternative

Instead of polling, use [Webhooks](/cloud/guides/webhooks) to receive status changes. Configure your webhook endpoint in the [dashboard](https://cloud.browser-use.com/settings?tab=webhooks), then add a **Webhook** trigger node in n8n to receive V3 `session.status.update` events. Match `payload.session_id` to the `id` saved from the create response, then check `payload.status` for completion. The `agent.task.status_update` event belongs to V2 tasks.

```json theme={null}
{
  "type": "session.status.update",
  "timestamp": "2026-09-09T12:00:00Z",
  "payload": {
    "session_id": "the-id-from-your-create-response",
    "status": "idle",
    "output": "The agent's result"
  }
}
```

Validate the signature before accepting a webhook. See the [verification example](/cloud/guides/webhooks#signature-verification); use a verified receiver in front of n8n if your workflow cannot perform that verification itself.

<Tip>
  This pattern works with any workflow tool that supports HTTP requests — Make, Zapier, Pipedream, or custom orchestrators.
</Tip>