Block reference / Browser

Update profile

Change a profile's name, notes or tags — the running one, a list, or a whole group.

Only inWarpX Browser

Update profile writes back how an account stands — verified, locked, the date it was last warmed up — so the Profiles page shows it and a later List profiles can find it. By default it changes the profile running the workflow; it can also change profiles you list or every profile in a group. It only touches the name, notes and tags: what a site sees of the profile stays as it is.

The Update profile block's settings, filled in as in the example below.

Settings

Description

A note shown on the block in the canvas.

ExampleMark as verified
Profiles

Which profiles to change: This profile (the one running the workflow, the default), These profiles or Every profile in a group.

ExampleThis profile
These profileswhen Profiles is These profiles

The box under the choice, with no label of its own. Ids or names separated by commas or lines, or a variable holding what List profiles found — the records or only their ids, both work.

Example{{variables.profiles}}
Every profile in a groupwhen Profiles is Every profile in a group

The group, picked from the ones on this computer (each shown with how many profiles it holds), or Id, name or variable… to type one. A group with no profiles fails the block with "That group has no profiles".

ExampleTikTok VN (20)
Namewhen Profiles is This profile

A new name. Left as it is when empty. Only offered for This profile: a name is changed on one profile at a time.

Example
Notes

Text to write into the profile's notes. Left as it is when empty — so this block cannot empty a profile's notes.

ExampleVerified {{$date('YYYY-MM-DD')}}
Add on a new line / Replace

The two choices under Notes. Add on a new line keeps each profile's notes and adds yours below them; Replace writes over them.

ExampleAdd on a new line
Tags

Tags separated by commas.

Exampleverified
Add / Remove / Replace all

The three choices under Tags, applied to each profile's own tags. Add keeps the ones it has; Remove takes these away, ignoring case; Replace all leaves only these — with Tags empty, it clears every tag.

ExampleAdd

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 block has no variable of its own; the log says what changed, such as tags verified, tiktok or 12 profiles · tags changed.

Example: Tag an account "verified" after the check passes

  1. Start
  2. New tab
  3. Element exists
  4. Update profile
Where Update profile sits in the example workflow.
  1. After your verification steps, add an Element exists block on [data-e2e="profile-icon"], the avatar that only shows when the account is signed in.
  2. Connect its top output to an Update profile block. Leave Profiles on This profile.
  3. Set Notes to Verified {{$date('YYYY-MM-DD')}} with Add on a new line.
  4. Set Tags to verified with Add.
  5. Connect the bottom output of Element exists to a second Update profile block with Tags need-check and Add.
  6. Run it on the group. On the Profiles page each account now carries verified or need-check.

Good to know

  • With nothing to change — no name, no notes, no tags and not Replace all — the block fails with "Nothing to change".
  • The Name box is hidden for a list or a group, but a name typed there earlier is still in the block. Clear it before switching Profiles, or a list of several fails with "Only one profile can be renamed at a time".
  • Profiles are changed one at a time, in the order listed. If one is refused, the block fails there: the profiles before it are already changed and the ones after it are not.
  • A profile, group or proxy is found by its id, or else by its name ignoring case. When two have the same name the block fails with "2 records are named … — use the id instead"; one that is not there fails with "No profile …".
  • Changing only the running profile never asks for confirmation. Changing a list or a group does: A workflow that was not edited on this computer (installed from the Appstore or a file) asks you to allow this block before its first run, in a window that lists what it will do. Blocks you set up in the editor are approved as you edit them, so your own workflows never ask; changing the block's settings asks again.
  • Needs the WarpX Browser desktop app, where the profiles are. Elsewhere the block is not in the block list, and a workflow that has it fails with "Profile and group blocks need the WarpX desktop app".
  • On an Appstore listing, a workflow with this block shows Lists, creates, opens, closes and changes your profiles, their groups and proxies.

See also

  • Profile info — Read the running profile's name, notes, tags, group and proxy into a variable.
  • List profiles — The profiles in a group, with a tag, open or closed — as records or as ids.
  • Move to group — Put profiles in another group, making the group first if you like.