Block reference / Browser

New tab

Opens an address in a new tab of the profile's browser and moves the workflow onto it.

Only inWarpX Browser

New tab opens a page in a new tab of the profile's browser. Every later block works in that tab. The block waits for the page to load before the workflow moves on. It can also reuse the tab the workflow is already in.

The New tab block's settings, filled in as in the example below.

Settings

New tab URL

The address to open. If you leave out https://, it is added for you. You can use references such as {{table.url}} or {{variables.startUrl}}.

Examplehttps://shop.example.com/login
Update previously opened tab

Tick it to open the address in the tab the workflow is already using, instead of a new tab. If the workflow has no tab yet, a new one opens anyway.

ExampleUnchecked
Wait until the tab is loaded

In WarpX Browser the block always waits for the page to load, so ticking this adds nothing.

ExampleChecked
Set as active tab

On: the tab is in front when the block ends. A tab that is already visible is not raised again. Off: the new tab opens, then the page before it is brought back in front. Later blocks work in the new tab either way.

ExampleChecked
Use custom User-Agent

Makes this tab send a different User-Agent. The block sets it, then reloads the page it opened, so the page is loaded again with yours. Later pages in the tab use it too. It is not available in every profile's browser, and where it is not, the block fails.

ExampleUnchecked
User-Agentwhen Use custom User-Agent is on

The unlabelled box under Use custom User-Agent, holding the User-Agent string to send.

ExampleMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
Delay time (ms)

A pause after the block, in milliseconds, such as 1000. Or a range such as 1000,3000 for a random pause each run.

Example1000,3000

Every block also has the shared block settings — a description, Disable block and what to do on an error. Fields that take text accept data from earlier blocks.

What it hands on

Leaves by its only output. The new tab becomes the one later blocks work in. The block writes nothing to the table or to variables.

Example: Open the sign-in page in its own tab

  1. New tab
  2. Forms
  3. Click element
  4. Element exists
Where New tab sits in the example workflow.
  1. Add New tab and set New tab URL to https://shop.example.com/login.
  2. Leave Update previously opened tab unticked, and set Delay time (ms) to 1000,3000 for a short, varied pause.
  3. Add Forms blocks for #email and #password, then Click element on button[type=submit].
  4. Add Element exists on .account-menu to check the sign-in worked.

Good to know

  • Each profile already has a User-Agent that fits its fingerprint. Overriding it for one tab can make that tab look inconsistent with the rest of the profile. Change the profile's settings instead where you can.
  • With a custom User-Agent the page loads twice: first with the profile's own User-Agent, then, after the reload, with yours. The site sees both.
  • To open a page in the tab you are already in, Open URL does the same job with more loading options.
  • The block fails if New tab URL is empty or is not a valid address.
  • The editor no longer offers Add tab to a group or Tab zoom. A browser under automation has no tab groups, and its zoom cannot be set. An older workflow that has them set runs as if they were not.

See also

  • Open URL — Load a web address in the current tab or a new one, and wait for it to load.
  • Switch tab — Move the run to another open tab, found by its address, its title or its position.
  • Close tab/window — Closes the tab the workflow is using, the tabs that match a pattern, or every window.
  • New window — Open a web address in a new window of the profile's browser, and carry on in it.