Build and activate automations
Purpose
Section titled “Purpose”Automations connect telemetry conditions to explicit actions using a visual workflow. Simulation and execution evidence help you check behavior.
Before you start
Section titled “Before you start”The organization must have automation enabled. Viewing requires workflow viewing permission; editing and activation have separate capabilities. Command actions also require command grants.
- Open Automations and choose Create automation or an existing workflow.
- In Editor, select devices and connect supported source, condition, and action nodes.
- Configure each node and save the draft.
- Use Simulation to check the saved revision.
- Review activation and its diagnostics, then activate explicitly.
- Wait for acknowledgment and inspect Execution for recorded evaluations.
Expected result
Section titled “Expected result”A saved draft is separate from the deployed generation. New evaluations use the acknowledged deployed version.
Troubleshooting
Section titled “Troubleshooting”Unconnected inputs, unavailable device settings, or missing command grants can block validation or activation. Layout edits do not establish execution behavior. Stop all automation actions, under Emergency stop at the bottom of Automations, asks for confirmation and then stops new action dispatch; already dispatched commands may still arrive.