Recording sequences

Browser Proxy (Recording Only)

The browser proxy is required only during traffic recording. It routes supported browser traffic through the recorder so it can be captured as steps in the sequence.

• Not needed for preview or timeline execution (these run through Leapwork cloud agents).

• Disable the proxy when not recording to avoid access errors.

• The CA certificate is required only when recording encrypted traffic.

Read more about proxy and certificate here: Create your first Sequence Create a self-signed certificate for recording traffic in Leapwork Go

Starting a Recording

1. Open your browser and navigate to the application you want to test.

2. In Go, click Record.

3. Choose the hostname you want to capture. Recording supports both single-host and multi-host configurations. For a single hostname, enter or select one hostname as before.

4. Click Start recording, then interact with your application (for example, refresh a page or submit a form).

5. Click Stop when finished to stop the recording.

Go automatically lists each network request as a step. You can expand any step to view details such as:

• Request and response payloads

• Headers and parameters

• Timing metrics and status codes

Recording traffic across multiple hostnames

Leapwork Go supports capturing traffic from more than one hostname within a single recording session. This is useful for complex environments where a single user interaction triggers requests across multiple services. For example, a primary API host and a separate authentication or analytics endpoint.

The behaviour depends on your Allowed URLs policy setting.

When Enforce Allowlist is ON

1. Click Record on a sequence.

2. A dropdown lists all hostnames pre-approved by your administrator under Settings → Policy Configuration → Allowed URLs.

3. Select one or more hostnames from the dropdown.

4. Click Start recording.

Only hostnames present in the approved list are available. If a hostname you need is missing, contact your administrator to add it to the allowlist.

When Enforce Allowlist is OFF

1. Click Record on a sequence.

2. In the hostname input field, enter one or more hostnames separated by commas.

   Example: api.example.com, auth.example.com, analytics.example.com

3. Click Start recording.

Recording will not start if the hostname field is empty or contains only whitespace. At least one valid hostname is required.

Existing single-host configurations are fully supported. Entering a single hostname continues to work as before.

Manually adding HTTP call

If you already have API requests defined, you can import them directly:

1. Right-click on an empty space inside a sequence

2. Click add HTTP call

3. Go now adds an empty HTTP call for you to add:

   1. Method - choose between GET, POST, PUT and DELETE

   2. URL

   3. Expected request:

      1. Parameters

      2. Headers

      3. Host

      4. Cookies

   4. Expected reponse:

      1. Status code

      2. Cookies

Manually adding cURL

If you already have API requests defined as cURLs, you can import them directly:

1. Right-click on an empty space inside a sequence

2. Click Paste cURL as HTTP step

3. Paste a bash or CMD cURL command.

4. Go automatically converts it into a structured HTTP step that can be edited, parameterized, and reused.

Exporting a step as a cURL command

You can export any existing HTTP step from a sequence as a cURL command. This is useful for sharing a request with a colleague, reproducing it in a terminal, or debugging it outside of Leapwork Go.

To copy a step as cURL:

1. Right-click the HTTP step in the sequence editor.

2. Select one of the following:

   • Copy as cURL (bash) — produces a Unix/macOS-compatible command.

   • Copy as cURL (CMD) — produces a Windows Command Prompt-compatible command.

3. Paste the copied command into your terminal or share it directly.

The exported cURL reflects the current state of the step, including its URL, method, headers, and request body.

Paste cURL automatic body type detection

When you use Paste cURL as HTTP step, Leapwork Go automatically identifies and sets the correct request body type based on the content-type header and body structure of the pasted command.

The following body types are detected and applied automatically:

You do not need to set the body type manually after pasting. If the detected type does not match your intent, you can change it in the step editor after import.

API step name and body type retention

API step names and body type selections are retained across browser tab refreshes and recording sessions. Changes made during authoring are not lost if you refresh the page or start a new recording.

Previewing Your Recording

Click Preview to execute your sequence. Go will:

• Run each recorded step.

• Display real-time execution progress with green indicators for success.

• Show per-step response times and results.

Once validated, rename your sequence for easy reference.