browser-use

n8n community node for Browser-Use REST API

Package Information

Downloads: 6 weekly / 132 monthly
Latest Version: 0.1.16

Documentation

@trg-admin/n8n-nodes-browser-use

n8n community node for the Browser-Use REST API.

Features

  • Submit browser automation tasks (POST /tasks)
  • Poll task status and result (GET /tasks/{task_id})
  • Download task recordings (GET /tasks/{task_id}/recording)
  • Manage session profiles (GET/POST/DELETE /profiles/...)
  • Start and monitor profile capture sessions for 2FA workflows
  • Preload saved profiles into dropdown selectors for task creation

Installation

npm install @trg-admin/n8n-nodes-browser-use

Credential Setup

Create a Browser-Use API credential in n8n:

  1. API Base URL: http://<your-server>:8000
  2. API Token: value configured as BROWSER_USE_API_TOKEN on your Browser-Use server (raw token or full Bearer <token> both supported)

API endpoints that require auth use Authorization: Bearer <token>.

Node Operations

Task

  • Create
  • Get
  • Get Recording

Get Recording always outputs binary data in the Recording field (default fallback file name uses .mp4).

Profile

  • Get Many
  • Get Capture Status
  • Upload
  • Delete

Capture

  • Start Session

Uploading Profile Files

For Profile -> Upload:

  1. Add a node that provides a binary file (for example, Read Binary File or an HTTP download).
  2. Set the node's binary property name in Input Binary Field (default: data).
  3. The file should be a Playwright storage_state JSON.

Note: task profile selection is populated from GET /profiles. Upload/delete/capture inputs use manual Profile ID values to avoid blocking execution if profile option loading fails.

API Alignment

This node is aligned with the documented Browser-Use API paths:

  • POST /tasks
  • GET /tasks/{id}
  • GET /tasks/{id}/recording
  • GET /profiles
  • POST /profiles/{id}
  • DELETE /profiles/{id}
  • POST /profiles/{id}/capture-session
  • GET /profiles/{id}/capture

License

MIT

Discussion