MLX API hub
Script Runner & Predefined Scripts
Run controlled script batches against Multilogin profiles with clear pass/fail thresholds—not endless silent retries.
When to use script runner
Use Multilogin’s script runner / predefined scripts when you need:
- Repeatable profile tasks without custom desktop tooling
- Bounded concurrency across many profiles
- A single place to observe success, timeout, and crash rates
This page is part of the MLX API Hub. For fully custom browsers automation, prefer Puppeteer or Selenium after profile start via API.
Operating contract
| Control | Recommended default |
|---|---|
| Concurrency | Start low (2–5); raise only after stable error rates |
| Timeout | Explicit per job; never “wait forever” |
| Failure threshold | Quarantine profile after N consecutive fails |
| Idempotency | Safe to re-run without duplicate side effects |
| Trace | Every batch gets a trace_id |
Batch skeleton
1. Resolve workspace + token (see workspace runbook)
2. Select profile set + script / predefined script id
3. Start profiles with automation flags as required
4. Execute script; capture stdout/stderr references
5. Stop profiles; write pass/fail + duration
6. Quarantine offenders; keep evidence pack
Failure thresholds
- Transient: network blip → retry once with backoff
- Profile-local: fingerprint/proxy issue → quarantine profile, do not retry blindly
- Systemic: API auth/5xx spike → halt batch, rotate or check agent health
Pred scripts vs custom
| Pred / built-in | Custom automation |
|---|---|
| Fast to trial | Full control of browser logic |
| Limited branching | Needs CDP/WebDriver discipline |
| Good for ops chores | Good for product-specific flows |
Next steps
- Confirm tokens via the workspace runbook.
- Prove one profile end-to-end before fan-out.
- Attach Puppeteer/Selenium only when pred scripts are insufficient.
- Keep Multilogin billing aligned with real usage — codes 50MAM / MAMOFF on the deals homepage.