Prepare one test profile
Install the public Windows release and create a clearly named browser profile, such as QA profile A. If your workflow needs a proxy, test the connection before using automation. Use a page you own or are authorized to test.
This example opens a page, waits for its main heading and scrolls down. It does not require a signed-in account. For a later account-based workflow, sign in to the correct account and confirm the profile context first.
Close a standard browser window opened for that profile before starting automation. In this release, the engine can report Close the standard browser before running an automation script on this profile.
It will open a browser for automation when needed.
Build a three-step workflow
- Open Automation and choose Create Script.
- Enter Page check in the Script Name field. Keep the platform as Other.
- Under Browser, drag New Tab / Navigate onto the canvas. Select the block and set its URL to a full address, including
https://, on a site you manage. - Add Wait for Element. Set CSS Selector to
h1if your target page has a main heading, and keep Timeout (ms) at10000. Otherwise, choose a selector that actually exists on that page. - Under Interaction, add Scroll. Choose Direction
downand Amount (pages)1. - Connect the blocks from Trigger in the order below. Disconnected blocks are not part of this sequence.
- Choose SAVE. The builder closes and returns you to Your Scripts.
Find Page check, choose Run, select only QA profile A, then choose Run on 1 profile. Check that the intended page opened and scrolled. On a short page there may be no visible scrolling because all content already fits in the window.
This is a setup walkthrough based on the public release's controls. Test it against your own target page; page structure and loading behavior determine the result.
Make the URL reusable
Edit the saved script and replace the Navigate block's fixed URL with {{pageUrl}}. Save it again. The builder turns this placeholder into a Page Url input in the run dialog.
Enter the complete target address each time you run the script. The other steps stay the same, so the new page must still contain the selector you chose. This lets you reuse the workflow without editing its URL for every run.
The ordinary parameter values you enter are shared across the profiles selected for that run. If two profiles need different URLs, run them separately with the appropriate input. Keep passwords and private account data out of saved example scripts.
Run on multiple browser profiles
- Create a second clearly named test profile and confirm its connection.
- Under Your Scripts, choose Run on the tested workflow.
- Under Select Profiles, select the two intended profiles. Check the selected count; avoid choosing every profile for your first test.
- Review the parameters, then choose Run on 2 profiles.
- Watch each profile in the status panel and inspect the result in each browser. Use Stop for an active run if needed.
Profile launches are staggered, so the windows may not appear at the same instant. Increase the number of profiles gradually according to available memory, CPU, connection quality and plan limits.
Each profile uses its own configured session and proxy settings. A shared script does not copy one profile's signed-in account into another. See multi-account management for how to organize those contexts.
Review results and troubleshoot
Completed is a status, not a result assertion. The public engine can continue after certain timeout or missing-element errors. Always check the expected page state yourself before expanding a workflow.
| What you see | What to check |
|---|---|
| The browser cannot start | Close the profile's standard browser window, confirm the proxy connection and try one profile again. |
| The wrong page opens | Check the full URL or Page Url parameter, including the protocol, and any redirect or sign-in screen. |
| A block does nothing | Confirm that it is connected from Trigger and that its selector matches the current page. A changed page layout may need a new selector. |
| A run says completed but the result is missing | Review the actual browser state. Simplify the workflow and test the uncertain action separately. |
| Multiple profiles make the computer slow | Stop the affected runs and reduce the number of selected profiles. Test with a smaller group before increasing it. |
The Stop control requests cancellation; an action already in progress may need time to finish. Stopping does not undo clicks, submitted forms or other changes already made.
Check streaming-platform workflows
For Twitch or Kick, distinguish routine account work from actions that affect audience metrics. Test the target URL and profile context manually before running a script. Do not treat a completed browser action as evidence of valid traffic or monetization eligibility.
Use the status panel to identify errors and stop repeated retries. A site change, login prompt or network issue can invalidate an otherwise working script.
Test e-commerce workflows carefully
For an approved store account, separate read-only checks from edits to listings, orders or customer information. Confirm the correct store in the launched profile and run a small test before making bulk changes.
Keep credentials and customer information out of shared logs. Review the five account-management habits and verify the proxy connection before scaling a workflow.
Work with social-platform accounts
Before running a workflow for YouTube, TikTok or Instagram, confirm that the selected browser profile is signed in to the correct authorized account. Test navigation and read-only steps first. Review platform rules and the consequences of any posting, following or other engagement action.
Do not use automation to fabricate audience activity or send unsolicited messages. Prefer approved platform tools or APIs when they support your task.