Overview

Maskifi scenarios are sequences of automation steps that run inside a browser profile. Each step — a click, a form fill, a navigation, an HTTP request — is called a block. You connect blocks into a flow; Maskifi executes them in the profile's browser.

What scenarios automate

Scenarios operate on the live browser that Maskifi launches for a profile. They can:

• Navigate to URLs and interact with pages (click, type, scroll, hover)
• Fill forms and submit them with human-like typing and random delays
• Extract text, attributes, or element counts from a page and store them as variables
• Make HTTP requests to external APIs and use the responses in later steps
• Branch on conditions, loop a fixed number of times or while a condition holds
• Run arbitrary JavaScript in the page context
• Open, close, and switch between browser tabs
• Work inside iframes (payment widgets, embedded forms)
• Log messages for debugging

When to use scenarios

Scenarios are most useful when you need to repeat the same browser actions across many profiles without manual work. Common uses include:

• Warming up profiles — navigate to sites, scroll, interact naturally before using a profile for serious tasks.
• Account registration flows — fill and submit sign-up forms with profile-specific data.
• Data collection — extract information from pages and send it to a webhook or API.
• Session maintenance — log in periodically so sessions stay active.
• Multi-step workflows — chain actions that depend on one another (log in, then extract a token, then call an API with it).

Where scenarios live

Scenarios are managed in the Automation section of the sidebar. A scenario is a saved, reusable flow. You can run the same scenario against one profile, several profiles at once, or a batch of freshly created profiles.

How execution works

When you run a scenario against a profile, Maskifi:

1. Opens the profile's browser (if it is not already open).
2. Executes each block in sequence.
3. Streams block-by-block status and log output back to the app so you can follow progress in real time.
4. Marks the run as completed or failed when it finishes.

Blocks that fail stop the scenario unless they are wrapped in a Try/Catch block, which lets you handle errors and continue.

---

Next: Scenario builder — using the visual editor to build flows.