Trigger Nodes
| Node | Use it for |
|---|---|
| Manual Trigger | Start a workflow from the UI or an explicit operator action. |
| Scheduled Trigger | Run a workflow on a recurring schedule. |
| API Trigger (Synchronous) | Accept an API request and return a workflow-generated HTTP response. |
| Trigger by Another Workflow | Make a workflow callable from another workflow. |
| Subflow Trigger | Start a workflow as an internal subflow. |
| Site Added | React when a new site is added. |
| Site Removed | React when a site is removed. |
| Site Offline | React when a site stops checking in. |
| Site Online | React when a site resumes heartbeats. |
| WAN Interface Offline | React when a WAN failover interface goes offline. |
| WAN Interface Online | React when a WAN failover interface comes online. |
| WAN Packet Loss | React when WAN packet loss is detected. |
| WAN Packet Loss Resolved | React when packet loss recovers. |
Altostrat And MikroTik Actions
| Node | Use it for |
|---|---|
| Altostrat API Call | Call SDX API endpoints from a workflow. |
| Get Site | Retrieve site details and configuration. |
| Get WAN Tunnel | Retrieve WAN tunnel details and status. |
| Get Resource Tags | Read tags from a resource. |
| Set Resource Tags | Add or update tags on a resource. |
| Attach Policy | Attach a policy to a site. |
| Detach Policy | Remove a policy from a site. |
| Update WAN Priorities | Change WAN failover priority order for a site. |
| MikroTik API | Run a real-time command against a site. |
| MikroTik Script | Dispatch a RouterOS script or configuration change to a site. |
Integration Actions
| Node | Use it for |
|---|---|
| Webhook/API Call | Send HTTP requests to external APIs. |
| SOAP Request | Call legacy SOAP services. |
| SSH Command | Execute commands on a remote server over SSH. |
| Send Email (SMTP) | Send an email through a configured SMTP server. |
| Send Notification | Send SDX notifications through configured notification channels. |
| Trigger Another Workflow | Start another workflow from the current workflow. |
Data And Document Actions
| Node | Use it for |
|---|---|
| AI Text Transform | Use an AI prompt to transform text or structured data. |
| Text Transform | Render text from workflow data using templates. |
| JSON Parser | Parse JSON input for later nodes. |
| Data Mapper | Map values into a new object or array shape. |
| Date Transform | Add, subtract, or format dates. |
| String Transform | Apply string operations to a value. |
| Validate Data | Validate data using rules before continuing. |
| Filter Array | Keep only array items that match conditions. |
| Markdown to PDF | Convert Markdown content into a PDF artifact. |
| Shorten Link | Create a shortened link from a long URL. |
| Ingest Metrics | Send custom metrics for monitoring and analysis. |
Network And Security Tools
| Node | Use it for |
|---|---|
| IPv4 Address Tool | Analyze an IPv4 address or CIDR range. |
| WireGuard Key Generator | Generate a WireGuard key pair or derive a public key. |
| CVE Scan Multiple IPs | Start an immediate CVE scan for multiple IP addresses. |
Conditions And Flow Control
| Node | Use it for |
|---|---|
| String Condition | Branch on text values. |
| Number Condition | Branch on numeric comparisons. |
| Date Condition | Branch on date or time logic. |
| Boolean Condition | Branch on true or false values. |
| Array Condition | Branch on array contents or count. |
| Resource Has Tags | Branch based on resource tags. |
| Switch | Create multiple branches from cases. |
| Logical Group (AND/OR) | Combine multiple rules into one decision. |
| Loop / Iterator | Process each item in a list. |
| Terminate | Stop the workflow and mark the path completed or failed. |
Selection Guidance
Use SDX actions for platform state
If the workflow needs site, tag, policy, WAN, notification, or script behavior, prefer built-in Altostrat nodes over generic HTTP calls.
Use data nodes before branching
Normalize payloads before conditions. Clean data makes workflow paths easier to test and debug.
Use vault-backed credentials
External APIs, SMTP, SOAP, SSH, and signing keys should read credentials from vault items rather than plain node fields.
Keep loops bounded
Use loops for small, deliberate lists. For fleet-wide device changes, consider scheduled scripts or purpose-built SDX actions.