NVK Browser Call APIInstall

Summary

Send a GET or POST request through a browser profile to the specified URL, with optional query parameters, headers, and a POST body. The operation returns the browser API response for each input item.

Inputs

• Environment — Choose Local, Docker, or Tunnel (Custom URL). Tunnel requires a tunnel URL. Local uses the local browser API; Docker uses the host Docker address.
• Profile ID (required) — ID of the browser profile to use.
• Method — GET or POST; defaults to GET.
• URL (required) — Request URL.
• Query Parameters — Optional name/value parameters passed to the browser API.
• Additional Headers — Optional name/value headers passed to the browser API.
• Tab Index — Browser tab index; defaults to 0.
• Auto Start Profile — Whether to auto-start the profile if it is not running; defaults to false.
• Send Body — For POST requests, whether to send a body; defaults to false.
• Body Content Type — When sending a POST body, choose form URL-encoded, form-data, JSON, n8n Binary File, or Raw. The selected type controls which body fields are used.
• Input Data Field Name — For an n8n Binary File POST body, the binary property to send; defaults to data.
• JSON Body — JSON content for a JSON POST body.
• Raw Body — Raw content for a Raw POST body.
• Body Parameters — For form-data bodies, add named text values or binary file parameters. Binary parameters refer to an incoming binary property, defaulting to data.
• Form Data — For form URL-encoded bodies, add name/value parameters.

Output shape

A list of n8n items, one per input item, containing the browser API response in json.

Each item is paired with its input item. The operation has a second output for errors when n8n continues on fail; in that case failures are returned as items with an error field. For successful POST responses containing a base64 data URL in data.data, the payload is also exposed as binary data.data and the JSON field is replaced with [Binary Data].

Links

• n8n community nodes installation guide