Altostrat SDX automation is built for network operations teams that need repeatable work without losing control. You can design visual workflows, run RouterOS scripts through the device job plane, store workflow secrets, and use AI-assisted surfaces to speed up diagnostics or script drafting. The key idea is simple: use the lightest automation tool that still gives you the right safety, auditability, and operational visibility.Documentation Index
Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
Automation Surfaces
Workflows
Build node-based automations with triggers, actions, conditions, loops, workflow chaining, logs, runs, and authorizations.
Scheduled scripts
Execute RouterOS scripts across sites through the SDX job model, with testing, scheduling, authorization, and per-site outcomes.
AI-assisted operations
Use AI to draft scripts, transform text in workflows, and accelerate operator tasks while keeping review and approval in your hands.
Choose The Right Tool
| Need | Use | Why |
|---|---|---|
| React to site, WAN, schedule, or API events | Workflows | The workflow engine gives you branching, variables, conditions, and logs. |
| Push RouterOS changes across one or more sites | Scheduled scripts | Scripts run through the platform’s asynchronous device job model and can be tested before rollout. |
| Transform payloads or create reports | Workflows | Data mapper, parser, text, PDF, notification, and integration nodes keep this work visible. |
| Draft a RouterOS script faster | AI script generation | AI can create a starting point, but you still review and test before execution. |
| Store tokens, passwords, or signing material | Workflow vault | Vault secrets are not exposed again after creation and can be referenced by workflow nodes. |
Safety Model
Automation in SDX should stay observable:- Give workflows clear names and descriptions.
- Keep destructive or network-changing actions behind deliberate authorizations.
- Test workflow nodes with representative context before activating the workflow.
- Use vault secrets instead of hardcoding credentials in node inputs.
- Use scheduled script test runs before multi-site execution.
- Review runs, logs, and per-site outcomes after every meaningful automation change.
Start Here
Build workflows
Learn the workflow canvas, node types, context, testing, and logs.
Review triggers
Choose between manual, scheduled, API, lifecycle, health, and workflow triggers.
Use vault secrets
Store and reference sensitive values safely.
Run scripts
Test, authorize, schedule, and monitor RouterOS scripts.