Scenarios — User Guide | YoBench

What the Scenarios module does

The module is a visual node-graph builder for automations: you connect blocks into a graph, the engine runs them sequentially or in parallel, and for browser blocks Chromium is driven via Puppeteer with a live preview right inside YoBench. Useful for RPA: parsing with interaction, auto-registration, load streams, data migrations, action chains with conditional logic.

What you get:

• 44 block types across 11 categories.
• Parallel execution — parallelSplit / parallelJoin fork and re-join branches.
• Conditional logic — ifElse, loop, switch.
• Browser automation via Puppeteer with an anti-detect profile (User-Agent, viewport, locale, timezone, geolocation, WebGL/Canvas/WebRTC noise).
• Live preview — JPEG frames from the active tab streamed into the YoBench window.
• Debugging — step-through from any node (scenarios:debug-start).
• Run history — scenario_runs (thread and error counters), scenario_executions (batched per-block log), scenario_template_snapshots (graph versioning).

Block categories (44 total)

• Flow (7) — start, end, badEnd, delay, note, parallelSplit, parallelJoin.
• Logic (3) — ifElse, loop, switch.
• Data (7) — setVariable, logMessage, fileRead, fileWrite, random, textProcess, globalVariable.
• Network (3) — httpRequest, cookieSync, captchaSolve.
• Browser (13) — navigate, click, setValue, getValue, waitFor, screenshot, evaluate, pageData, tabSettings, fileUpload, requestIntercept, dialogHandler, dialogWait.
• Emulation (4) — mouseMove, keyboard, scroll, touchEvent.
• Email (2) — sendMail, receiveMail.
• Code (1) — javascript (arbitrary JS in a sandbox).
• Database (1) — sqlQuery.
• FTP (2) — ftpUpload, ftpDownload.
• Proxy (2) — proxyRotate, proxyCheck.
• Project (2) — runSubScenario, setProfile.

Scenario parameters

• Graph — nodes and edges, serialized as JSON.
• Browser profile — User-Agent, viewport, locale, timezone, geolocation, fingerprint noise (WebGL/Canvas/WebRTC).
• Concurrency (thread_count) — how many copies run in parallel.
• Repetitions (execution_count) — how many times to execute.
• Run timeout (run_timeout).

There are no scenarios* keys in central settings — parameters live per scenario (scenarioSettings).

Triggers

• Manual — the Run button or IPC scenarios:start with templateId.
• Debug — scenarios:debug-start, you can start from any node (startNodeId).

Live preview and debugging

• Preview — scenarios:start-preview attaches to the chosen Chromium tab; frames come over IPC scenarios:preview-frame as base64 JPEG.
• Step debug — block-by-block execution with variable and browser-state inspection.

Storage and logs

• scenario_runs — status, start/end time, thread and error counters.
• scenario_executions — batched log of every block call with JSON params and result.
• scenario_template_snapshots — graph versions.

Workflow

1. Open the Scenarios module from the left sidebar.
2. Create a scenario, drag blocks onto the canvas and connect them.
3. Configure the browser profile (User-Agent, viewport, ...).
4. Run — watch the flow in the live preview.
5. Use Debug — step through from any node.
6. Compare runs in the scenario_runs history.

Next steps

• Scenarios can embed each other via runSubScenario — reusable subgraphs.
• Use Web Parser for static sites and Site Audit for SEO/Lighthouse — Scenarios is for cases that need interaction.
• For load — Load Testing.

Help and feedback

Want cron triggers, webhooks, or a template marketplace? Contact us via the feedback form.