An automation watches for something happening and does something about it.
Automations require a Pro plan or higher.
Every rule has three parts: a trigger, optional conditions, and one or more actions.
Event - fires when something happens in AssetBolt.
Schedule - fires on a cron schedule.
Manual - fires only when you run it.
Devices - created, updated, deleted, assigned, unassigned, status changed, location changed
Accessories - created, updated, low stock
Consumables - created, updated, low stock, out of stock
Licenses - created, updated, expiring, expired
People - created, updated, deactivated
Integrations - connected, disconnected, sync completed, sync failed
Cloud and data assets - discovered, updated, removed, became public
Maintenance - created, completed, overdue
Asset requests - created, approved, denied, fulfilled
Warranties - expiring, expired
Audits - due, overdue
Conditions filter which events actually run the rule, combined with AND / OR logic. A rule with no conditions runs on every matching event.
An automation can:
Send a notification
Send an email
Send a webhook
Update a field
Assign an asset
Unassign an asset
Change a status
Add a tag
Write an audit-log entry
Create a ticket
Trigger a sync
Send a Slack message
Send a Microsoft Teams message
Both actions need connected chat integration and message text. You can also set:
A channel to post to, or leave it blank to use the default channel configured for that integration.
A title (Microsoft Teams only). Teams renders it as a bold heading on an Adaptive Card. Slack ignores it.
Message text supports the same dynamic fields as other automation actions, like the triggering asset's name or the error from a failed sync.
Eight built-in templates cover the common cases:
Notify when a license expires in 30 days
Alert on low-stock accessories
Write an audit-log entry on device status changes
Send a webhook on new asset requests
Return devices when a person is deactivated
Notify on overdue maintenance
Alert on integration sync failures
Tag newly created devices as "needs-setup"
Each rule can be toggled active or inactive, test-run, duplicated, or deleted. An execution history shows what ran and what happened.
The automations page summarises total rules, active rules, total executions, and recent failures.
A rule that keeps failing is paused automatically. This stops a broken webhook from retrying forever.
A paused rule shows as Paused. When AssetBolt tries it again it shows as Retrying. Rules are also rate-limited.
If a rule you rely on has gone quiet, check whether the circuit breaker has paused it.
