All posts

Managing Multiple Browser Profiles in Broma for Safe Multi‑Account Workflows

Managing Multiple Browser Profiles in Broma for Safe Multi‑Account Workflows

Why Isolate Browser Profiles?

When you run repetitive web tasks, each account often needs its own set of cookies, saved logins, and browser extensions. If all actions share a single profile, data from one account can bleed into another, causing:

  • Accidentally posting to the wrong store.
  • Losing session state when a page reloads.
  • Triggering anti‑bot mechanisms that look for multiple accounts from the same browser.

Isolating profiles gives you a clean, self‑contained environment for every task, which improves reliability and reduces the risk of account bans.

Benefits of Profile Isolation

  • Credential safety – each profile stores its own login cookies, so you never reuse a password across accounts.
  • Extension hygiene – add a price‑tracker extension to one profile without it interfering with another.
  • Testing flexibility – run the same workflow against different site layouts (e.g., mobile vs desktop) by switching profiles.
  • Auditability – logs show which profile performed each action, making troubleshooting easier.

Setting Up Profiles in Broma

Step 1: Create a New Profile

  1. Open Broma and go to Profiles → New Profile.
  2. Give the profile a descriptive name, e.g., Amazon_Seller_A.
  3. Choose a platform (Chrome, Edge, Firefox) – Broma uses the underlying engine of the selected browser.

Step 2: Configure Cookies, Logins, and Extensions

  1. After creation, click Edit.
  2. Use the Import cookies button to paste a cookie string exported from the target site, or manually add them via the Add cookie dialog.
  3. For login steps, add a Navigate action followed by a Fill form action that enters the username and password. Save the workflow as part of the profile so it runs automatically when the profile is activated.
  4. Install any required extensions by toggling the Enable extension switch; Broma will launch the browser with that extension already loaded.

Step 3: Assign a Proxy (Optional)

If the site restricts requests by IP, configure a proxy in the profile settings. Enter the proxy address, port, and authentication details. The profile will now route all traffic through that IP, keeping each account’s traffic separate.

Switching Between Profiles During a Workflow

Broma lets you insert a Run on profile action. This tells the workflow to:

  1. Activate the chosen profile.
  2. Execute the subsequent steps.
  3. Return to the original profile when finished.

Typical pattern:

  • Open page (profile‑agnostic URL).
  • Run on profile → Select Amazon_Seller_A.
  • Click the dashboard link.
  • Run on profile → Select Amazon_Seller_B.
  • Loop through steps for each profile.

This approach eliminates the need to manually change profiles between runs, making the workflow fully automated.

Real‑World Example: Managing Multiple E‑Commerce Seller Accounts

Scenario Overview

A seller operates three Amazon storefronts, each with its own login, pricing rules, and inventory. The goal is to:

  • Check the current buy‑box price on each storefront every 6 hours.
  • Record the price in a Google Sheet.
  • Send an alert if the price drops below a threshold.

Building the Workflow

  1. Create three profiles – Amazon_A, Amazon_B, Amazon_C – each pre‑filled with the respective seller login.
  2. Start a new workflow called Price‑Monitoring.
  3. Add an Open page action with the Amazon Seller Central URL.
  4. Insert a Run on profile action and select Amazon_A.
  5. Inside that sub‑workflow:
    • Click the Inventory tab.
    • Wait for element with selector //span[contains(@class,"price")] (see code block below).
    • Read text → store in a variable priceA.
    • If priceA < threshold → Send email (using a mail action).
  6. Add another Run on profile for Amazon_B and repeat steps 5‑6.
  7. Add a final Run on profile for Amazon_C.
  8. End the workflow with a Log action that records the timestamp and each price.

Code Block – Robust Price Selector

// XPath that survives minor class name changes
xpath = "//span[contains(@class, 'price')]//text()"

The expression uses contains to match any class that includes the word price, making it resilient when Amazon updates its HTML.

Running the Workflow

Set the schedule to Every 6 hours in the Scheduler tab. Broma will launch each profile in turn, execute the actions, and write a detailed log entry for each run. You can view the log per profile, making it easy to spot which account triggered an alert.

Maintaining Profiles When Pages Change

Even with robust selectors, a site redesign can break a workflow. Follow these practices:

  • Use stable attributes such as data-testid, id, or name whenever possible.
  • Add fallback selectors: if the primary XPath fails, include a secondary one separated by a pipe (|).
  • Test after each site update: run the workflow manually on each profile and verify that the read‑text step returns a value.
  • Version your profiles: when a major UI change occurs, duplicate the profile, make adjustments, and keep the original as a backup.

Scheduling and Logging

Broma’s built‑in scheduler lets you set:

  • Frequency (every hour, daily, weekly).
  • Start time and timezone.
  • Run limit (stop after N attempts).

Each scheduled run creates a log entry that includes:

  • Profile name.
  • Start and end timestamps.
  • List of actions executed.
  • Any errors with stack traces.

You can export logs as CSV for further analysis or feed them into a monitoring dashboard.

Troubleshooting Common Issues

Issue Likely Cause Fix
Profile fails to load cookies Cookie import error or missing domain attribute Re‑export cookies from a fresh browser session and re‑import.
Selector not found Element’s class or ID changed after a site update Update the XPath/CSS selector; use contains or a more generic attribute.
Proxy authentication error Wrong credentials or proxy blocked Verify proxy details in profile settings; test connectivity with a simple request.
Email not sent SMTP settings incorrect Check Broma’s mail action configuration; use a test email address.

Quick Checklist

  • Profiles created with correct login data.
  • Each workflow references the appropriate profile via Run on profile.
  • Selectors use stable attributes or contains logic.
  • Schedule set and a test run logged without errors.
  • Alerts and logging configured for the specific use case.

Conclusion

Isolating browser profiles in Broma gives you the same reliability that a dedicated RPA server provides, but without the overhead of cloud services or code. By creating dedicated profiles for each account, you keep cookies, extensions, and proxies separate, which prevents cross‑contamination and reduces the chance of account bans. The step‑by‑step setup, profile‑switching actions, and robust selector strategies make it straightforward to build repeatable, maintainable workflows for e‑commerce sellers, marketers, and anyone who needs to manage multiple web identities from a single Windows desktop.