Linken Sphere 2 Scenarios — A No-Code Automation Pipeline
How Linken Sphere 2 Scenarios actually work: blocks, variables, branching, scheduling, and real-world examples for affiliate teams.
Linken Sphere 2's Scenarios is the deepest no-code automation engine in any anti-detect browser. Here's how it actually works and what to build with it.
Core concepts
- Blocks — atomic actions: navigate, click, type, wait, conditional, HTTP request, variable set.
- Variables — per-profile key-value store. Persistent across scenario runs.
- Branches — conditional flow based on variable values or DOM state.
- Retries — exponential backoff on block failures.
- Schedule — cron-like, timezone-aware, runs per profile or per group.
Example: FB account warming
Build a scenario that:
- Navigates to facebook.com
- Waits for page load
- If logged out → branch to login flow
- Scrolls feed for 5-15 minutes (randomised)
- Likes 2-4 posts (randomised)
- Adds 1-3 friend suggestions
- Logs out
- Schedules itself to repeat in 18-30 hours (randomised)
The scenario runs per profile across 100 profiles, randomising actions enough that detection doesn't see identical patterns.
Example: ad spend monitoring
- Logs into FB Ads Manager
- Reads daily spend across all active campaigns
- Posts results to your Slack via HTTP block
- If spend exceeds threshold, pauses campaigns
- Logs out
Scheduled every 30 minutes across all your FB Ads profiles.
Example: Amazon multi-listing
- Reads listings.csv from variable store
- For each row, navigates to Amazon Seller Central
- Creates listing with row data
- Captures listing URL into variable
- Posts URL + ASIN back to your CRM
Where scenarios beat raw Selenium
- No engineering bandwidth required — operators build flows visually.
- Per-profile state persistence — variables survive across runs.
- Built-in scheduling — no separate cron / Airflow.
- Visual debugging — see exactly which block failed and why.
Where scenarios fall short
- Complex logic — deeply nested branching gets unwieldy. Drop to Selenium / Playwright for genuine complexity.
- Custom libraries — no way to import npm packages.
- Engineering team prefers code — for teams with engineers, Afina's Selenium / Playwright API is more flexible.
See our Selenium / Playwright on anti-detect guide for the code-first alternative.
When to pick LS2 for scenarios
If your team has more operators than engineers and your workflows are 80% repetitive — LS2 Scenarios collapses three tools (anti-detect + automation + scheduler) into one product. Worth the higher entry price.