Introduction
Delete device removes the device record and its associated alert history, custom field values, applied tag assignments, and automation run history from the live Level service when an automation runs. Use this as the final step in an offboarding automation to clean up devices that have been decommissioned or are no longer reporting.
⚠️ WARNING: This action cannot be undone through the product. It removes the device record and the device-specific data listed below from the live Level service. Reinstalling the agent creates a new record and does not restore deleted history. Use Conditions to verify the intended targets before enabling the automation. Residual copies in restricted database backups are handled separately under our Cancellation Policy.
Residual backups and required records. Our Cancellation Policy and Privacy Policy describe the following terms:
Where permitted by applicable law and Standard Contractual Clauses, residual personal data that cannot reasonably be selectively erased from routine encrypted database backups may remain for up to 365 calendar days from each backup's creation. This is a maximum, not a guaranteed recovery period. For a terminated service, a backup created before active-system deletion may contain data for up to 425 days after termination. Residual data is isolated from ordinary use and restricted to controlled disaster recovery or a specific legal obligation; completed deletions are reapplied before restored data returns to ordinary use or another backup is made. Copying or restoring a backup does not restart the period. Specific legally required preservation and minimum business records kept lawfully for separate purposes are handled as described in the Cancellation Policy and Privacy Policy. A shorter deadline in law or a signed agreement takes precedence.
Delete Device
This action has no configuration options. The deletion applies to the device the automation is running against.
💡 TIP: Add a Conditions gate on this action (for example, require a specific tag or custom field value) as a second layer of protection beyond your trigger. This prevents accidental mass deletion if the automation fires against unintended devices.
Because there are no configuration options here, all targeting precision comes from your automation's trigger and Conditions. Set these carefully.
ℹ️ NOTE: Deleting a device record and removing the agent from an endpoint are separate operations. Deletion from Level does not confirm that the software has been removed from the endpoint. An offline or unreachable endpoint may require local removal. See Uninstall Level for removal instructions.
Conditions
The Conditions section lets you restrict when this action runs based on device attributes or the outcome of a previous action.
See Action Conditions for the full reference on condition types, operators, and values.
Additional Options
Expand Additional options for action name, failure behavior, output variable assignment, retries, and the enabled toggle.
See Actions Overview for the full reference on additional options available on every action.
FAQ
Is deletion reversible? No. You cannot restore the deleted record or its history through the product. Re-enrollment creates a new device record. Restricted backup retention does not make this action reversible or provide an account-restoration service.
Does deleting a device uninstall the Level agent? Not necessarily. Deletion removes the hosted device record, but does not confirm that the Level agent has been removed from the endpoint. An offline or unreachable endpoint may require local removal. See Uninstall Level for removal instructions.
What data is deleted? The device record, alert history, custom field values, applied tag assignments, and automation run history associated with that device are removed from the live service on successful deletion. This action is not deletion of the workspace. It does not mean that every related record or backup copy disappears. Our Cancellation Policy and Privacy Policy describe how residual backups and separately retained records are handled.
Who can configure this action? Any technician with permission to create or edit automations. Given the destructive nature of this action, consider restricting automation editing permissions to senior technicians.