NVK Browser Call API icon

NVK Browser Call API

Interact with NVK Browser API for automation

Actions12

Browser Automation → Run Multiple Profiles

AI-generated

Summary

Runs one task for each nonblank line in the Data field, arranging tasks in a grid and either processing them sequentially or in concurrent batches. It returns per-line results and can send each result to an optional webhook.

Inputs

  • Environment (required) — Connection environment: Local, Docker, or Tunnel. Tunnel requires a Tunnel URL.
  • Tunnel URL (required) — Base URL for the tunnel environment; shown only when Environment is Tunnel.
  • Data (required) — One task per line, formatted as line|profileId. The implementation uses each line's pipe-separated parts to build the task response.
  • Number of Threads — Batch concurrency when waiting for the previous session is disabled; defaults to 1.
  • Define Columns — Grid columns used to calculate each task's window position and size; defaults to 3.
  • Define Rows — Grid rows used to calculate each task's window position and size; defaults to 2.
  • Win Scale — Percentage used to scale the calculated window dimensions; defaults to 100.
  • Webhook URL — Optional URL to receive each task result. GET sends result fields as query parameters; POST sends a JSON body.
  • Webhook Method — Webhook method, GET or POST; defaults to POST.
  • Timeout (Milliseconds) — Timeout value included in the operation result; defaults to 100000000.
  • Wait For The Previous Session To Complete — When enabled (default), processes tasks sequentially. When disabled, processes batches using Number of Threads.

Output shape

A single result object containing a results array with one success or error record per processed line.

The result includes task counts, execution mode, thread and grid settings, timeout, and a message; it also includes webhookSummary. Each successful record contains the original line, thread ID, calculated window position and size, and a response built from the line's pipe-separated parts. Task failures are recorded in results rather than aborting the operation. Webhook delivery failures are logged and do not fail task processing.

Examples

Example 1: sample

Example only

Links

Discussion