Browser Use OrchestratorInstall

Summary

Waits for a previously launched Browser Use job to finish and returns its current state and result. Calls the orchestrator's MCP await_job tool, blocking up to the given number of seconds.

Inputs

• Job ID (required) — The job_id returned by Run Task Agent, Run Vision Agent, Fetch Page, or another job-producing operation run in async mode (or in sync mode if it timed out).
• Wait Seconds — Additional Field. Maximum synchronous wait, 0–600. The field's description says the default is 120s. If you leave it unset, the node sends no wait_seconds, so the server applies its own default. Blocks until the job finishes or the wait expires. 0 returns the current state immediately.

Output shape

One output item per input item, containing the job state object from the orchestrator. It includes a status and, once finished, the result. The job_id is also present while the job is running.

Terminal statuses are done, error and cancelled. If the wait expires first, the job is still running and you get its current state. The job continues server-side, so you can call Await Job again. The HTTP timeout is wait + 30s, capped at 660s. MCP errors fail the item, or return {error} if Continue On Fail is on. If the tool returns non-JSON text, the output is {text}.

Examples

Example 1: Collect the result of a long-running task agent that was launched asynchronously.

Job ID = {{ $json.job_id }}; Wait Seconds = 300.

Example 2: Check job progress without blocking.

Job ID = the job's id; Wait Seconds = 0 to get the instant status.

Links

• n8n community nodes installation guide