Automations

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.

Triggers

Event - fires when something happens in AssetBolt.

Schedule - fires on a cron schedule.

Manual - fires only when you run it.

Events you can trigger on

• 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

Conditions filter which events actually run the rule, combined with AND / OR logic. A rule with no conditions runs on every matching event.

Actions

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

Templates

Eight built-in templates cover the common cases:

1. Notify when a license expires in 30 days

2. Alert on low-stock accessories

3. Write an audit-log entry on device status changes

4. Send a webhook on new asset requests

5. Return devices when a person is deactivated

6. Notify on overdue maintenance

7. Alert on integration sync failures

8. Tag newly created devices as "needs-setup"

Running and watching rules

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.

The circuit breaker

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.