What triggers can I use in a workflow?
A trigger defines what event starts a workflow. When the trigger event occurs, Velory automatically runs the workflow. Each workflow has exactly one trigger.
Before you begin
You need Admin access. Triggers are selected when creating or editing a workflow in the visual editor.
Available triggers
General
| Trigger | What starts the workflow |
|---|---|
| Manual | You trigger it by hand — useful for on-demand tasks |
| Scheduled | Runs on a recurring schedule (e.g. daily at 9am, every Monday, first of the month) |
| Webhook | Triggered by an HTTP request from an external system |
State and lifecycle changes
| Trigger | What starts the workflow |
|---|---|
| State Change | When an asset or employee's state changes (e.g. from "Active" to "In Repair") |
| Lifecycle Change | When a lifecycle stage changes (e.g. from Active to Inactive) |
| Group Membership | When someone is added to or removed from a group |
Employee events
| Trigger | What starts the workflow |
|---|---|
| Employee Joined | When a new employee is onboarded |
| HRIS Events | When an employee is created, updated, or deleted via an HRIS sync (BambooHR, Hailey HR, HiBob, Google Workspace, Entra ID) |
Contract and lease events
| Trigger | What starts the workflow |
|---|---|
| Contract Renewal Eligible | When a contract enters its renewal window |
| Disposition Needed | When a device needs a disposition decision |
| Disposition Completed | When a disposition is finished |
| Lease Payment Due / Overdue | When a lease payment is due or past due |
| Lease Ending | When a lease is approaching its end date |
Ticket and task events
| Trigger | What starts the workflow |
|---|---|
| Ticket Linked / Status Changed / Comment Added / Resolved | When helpdesk ticket events occur |
| Task Completed / Assigned / Decision Made | When task events occur |
| Project Created / Completed | When project lifecycle events occur |
Store and import events
| Trigger | What starts the workflow |
|---|---|
| Order Item Status Changed | When a store order's status changes |
| Import Candidate Created | When a reconciliation candidate is created during import |
Configuring triggers
Each trigger has specific options. Some examples:
- State Change — Select the entity type (asset or employee), and optionally specify the "from" and "to" states to narrow when it fires.
- Scheduled — Choose frequency (every 5 minutes, hourly, daily, weekly, monthly), time, and timezone.
- Webhook — Define the expected payload fields with their types (string, number, boolean) for validation.
- Group Membership — Pick a specific group or "any group", and whether the trigger fires on add or remove.
Good to know
Can I have multiple triggers on one workflow?
No. Each workflow has exactly one trigger. If you need the same actions to run for different events, create separate workflows for each trigger — you can duplicate an existing workflow to make this quick.
What is the difference between State Change and Lifecycle Change?
State Change fires when the specific operational state changes (e.g. "Available for use" → "In Use"). Lifecycle Change fires when the broader lifecycle stage changes (e.g. "Active" → "Inactive"). Lifecycle encompasses multiple states — use it when you care about the high-level phase, not the specific state.
How precise is the Scheduled trigger?
You can schedule workflows to run at specific intervals (every 5 minutes up to monthly) or on specific days and times. Times are configured in your chosen timezone.
Was this article helpful?