How To Use Trigger Nodes
- Choose one trigger only for the workflow entry point.
- Configure trigger-specific parameters (schedule, event source, or API mode).
- Connect trigger output to the first processing step.
- Test with representative payloads and verify downstream context values.
Choosing The Right Trigger
- Use Scheduled Trigger for recurring maintenance and reporting.
- Use API Trigger (Synchronous) when another system must invoke workflow execution directly.
- Use SNS-based lifecycle/health triggers for event-driven automation from platform signals.
- Use Workflow Trigger to create reusable callable sub-workflows.
Trigger Types
Manual Trigger
Start this workflow via an API call or the UI.View
Trigger by Another Workflow
Call this workflow from another workflow.View
Scheduled Trigger
Run this workflow on a recurring schedule.View
API Trigger (Synchronous)
Trigger this workflow via API call with synchronous execution.View
Site Added
Trigger this workflow when a new site is added.View
Site Removed
Trigger this workflow when a site is removed.View
WAN Interface Offline
Trigger when a WAN interface from a WAN failover goes offline.View
WAN Packet Loss
Trigger when a WAN interface from a WAN failover experiences packet loss.View
WAN Packet Loss Resolved
Trigger when a WAN interface from a WAN failover recovers from packet loss.View
WAN Interface Online
Trigger when a WAN interface from a WAN failover comes online.View
Site Offline
Trigger when a site fails to check in with the management system for more than 5 minutes.View
Site Online
Trigger when a site comes back online and resumes sending heartbeats.View
Registry-Only Trigger Entries
These exist in the automation registry but are excluded from prompt-assistant context (for example, subflow-only nodes).Subflow Trigger
This trigger is activated when a subflow is called.View
Trigger Design Best Practices
- Keep trigger configuration minimal and deterministic.
- Validate expected input schema before downstream processing.
- Add guard conditions early when trigger payloads can vary.
- Monitor missed or delayed executions for schedules and external callbacks.