Block reference / Browser

Profile info

Read the running profile's name, notes, tags, group and proxy into a variable.

Only inWarpX Browser

Profile info tells a workflow which account it is working in. It reads the profile running the workflow and puts its id, name, notes, tags, OS, country, IP, group and proxy in a variable, so later blocks can type the profile's name into a form, look its row up in a sheet, or branch on a tag. To read some other profile, use Get profile.

The Profile info block's settings, filled in as in the example below.

Settings

Description

A note shown on the block in the canvas.

ExampleWhich account is this?
Assign to variable

On by default. When off, the block reads the profile and only the log shows it.

ExampleChecked
Variable namewhen Assign to variable is on

The variable that gets the profile. The default is profile, read as {{variables.profile.name}}, {{variables.profile.tags}} and so on.

Exampleprofile

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

One output. The variable holds id, name, notes, tags (a list), os, country, ip, folder (the group's name) and proxy — type, host, port, username and name, or empty when the profile has no proxy. The proxy's password is never included. The log shows the profile's name.

Example: Skip accounts that are already verified

  1. Start
  2. Profile info
  3. Conditions
  4. New tab
Where Profile info sits in the example workflow.
  1. Add a Profile info block and leave Variable name as profile.
  2. Add a Conditions block with a path named Already verified: {{variables.profile.tags}} Contains verified.
  3. Leave Already verified unconnected, so the run ends there for those profiles.
  4. Connect Fallback to a New tab block on https://www.tiktok.com/login and the rest of your verification steps.
  5. Run it with Run automation on the whole group: profiles tagged verified stop after the check, the others go on.

Good to know

  • It always reads the profile the workflow is running in. In the editor that is the profile the editor runs in; in Run automation it is each profile in turn.
  • Needs the WarpX Browser desktop app. Elsewhere it fails with "Profile blocks need the WarpX desktop app, where a workflow runs in a profile".
  • The values are read when the block runs. After an Update profile block changes the tags, run Profile info again to see the new ones.
  • On an Appstore listing, a workflow with this block shows Reads or changes this profile's name, notes and tags.

See also

  • Update profile — Change a profile's name, notes or tags — the running one, a list, or a whole group.
  • Get profile — Read any profile on this computer by its id or name, with a fallback when it is not there.
  • Conditions — Send the run down one of several paths, depending on values, page elements or code.