Project Automations
Automations let you define rules that trigger actions automatically based on case events. Instead of manually assigning, escalating, or updating cases, automations do the repetitive work so your team can focus on what matters.
Automation List View
Navigate to your project and click Automations in the right workspace sidebar to see the full list.
The list shows all automations with the following columns:
| Column | Description |
|---|---|
| Status | Toggle to enable or disable the automation |
| Automation Name | Clickable name that opens the automation for editing |
| Created by | User who created the automation |
| Created On | Date the automation was first saved |
| Updated On | Date of the most recent change |
| Actions | Three-dot menu: edit, duplicate, delete |
Automation Tabs
The Automations page has four tabs:
Automations
The main list of all saved and active automations. Use the Status toggle to enable or disable individual automations without deleting them.
Activity
Shows a log of which cases have triggered each active automation — including timestamps and outcomes. Use this tab to confirm that automations are running correctly and to audit recent automation behavior.
Upcoming
Shows cases that are predicted to trigger an automation in the near future. For example, a "Due in 3 days" trigger would show cases approaching that threshold. Use this to anticipate workload and spot cases that may need manual attention before automation fires.
Drafts
Lists automations saved as drafts — either manually saved as draft or auto-saved while you were building. Drafts are not active and do not trigger until you publish them.
Auto-save: The canvas builder automatically saves your work as a draft as you build. You will never lose an in-progress automation due to an accidental navigation or browser close.
Creating an Automation
Click Create automation (top right of the Automations list) to open the canvas builder.
Canvas Builder
The builder has two areas:
Left panel — Step Library Browse available step types across three tabs:
- Triggers — What causes the automation to start
- Actions — What happens when the automation fires
- Conditions — Filters to narrow when the automation applies
A Search by step name field at the top of the panel lets you quickly find any trigger, action, or condition by name.
Canvas — Visual Flow A drag-and-drop canvas where you build the automation visually:
- Drag a Trigger block from the panel onto the "Add Trigger" slot
- Configure the trigger settings
- Drag an Action block onto the "Add Action" slot below
- Configure the action settings
- Add more Actions or Conditions as needed
- The flow ends at the Exit node at the bottom
Title field (top left) is required — enter a descriptive name before creating. The Create button activates once the automation has a title and at least one trigger and action.
Avia AI in the Automation Builder
The builder includes an Avia AI tab alongside the standard Builder tab. Switch to Avia AI to describe the automation you want in plain language and let the AI generate the flow for you.
How it works:
- Click the Avia AI tab in the right panel
- Describe what you want the automation to do (e.g., "When a high-priority case is created, assign it to the senior team and notify the manager")
- Avia AI generates a suggested automation flow on the canvas
- Preview the generated flow to review triggers, actions, and conditions
- Accept to apply the suggestion, or Edit to adjust individual steps before saving
- Publish the automation when ready
Tip: You can use Avia AI to build a starting point and then switch back to the Builder tab to fine-tune the steps manually.
Available Triggers
| Trigger | When it fires |
|---|---|
| New case | When a new case is created |
| Status | When the case status changes |
| Priority | When the case priority changes |
| Assignee | When the case is assigned or reassigned |
| Created by | When a case is created by a specific user |
| Start date | When the start date is set or changed |
| Due date | When the due date is set, changed, or approaching |
| Description | When the case description is updated |
| Queue | When the case is moved to a different queue |
| Email received | When an email is received on the case |
Available Actions
- Add to queue — Move the case into a specified queue
- Change assignee — Assign the case to a specific user
- Change priority — Set the case priority level
- Change status — Update the case status
- Change due date — Set or adjust the due date
- Add comment and mention — Post a comment and mention the case creator, assignee, watchers, or a specific email address
- Send notification — Send a notification to specified recipients
Conditions
Conditions act as filters that must be satisfied before the action fires. Multiple conditions can be combined using AND (all must be true) or OR (any must be true) logic, across one or more condition groups.
Operators
| Operator | Meaning |
|---|---|
| is | Field exactly matches the value |
| is not | Field does not match the value |
| one of | Field matches any value in a list |
| not one of | Field does not match any value in a list |
| to | Field changes to a specified value |
| date is | Date field is exactly a specific date |
| date before | Date field is before a specific date |
| date after | Date field is after a specific date |
| added | Value was added to the field |
| changed | Field value changed (any value) |
| removed | Value was removed from the field |
Automation Examples
Priority-Based Assignment
Trigger: Priority changes to "High"
Action: Assign to senior team member + notify project manager
SLA Reminder
Trigger: Due date is 1 day away
Action: Notify current assignee with a reminder
Overdue Escalation
Trigger: Due date has passed
Action: Change status to "At Risk" + notify manager
Auto-Route New Requests
Trigger: New request created
Condition: Case type = "Bug Report"
Action: Move to Support queue + assign to on-call agent
Best Practices
- Start with one trigger and one action — add complexity once it's working
- Use the Activity tab after enabling an automation to confirm it's firing correctly
- Check Upcoming regularly to anticipate high-volume automation runs
- Save as Draft first and review before publishing to production
- Give automations descriptive names so the list stays manageable
- Disable rather than delete automations you might reuse
Troubleshooting
Automation not triggering?
- Confirm the automation is enabled (Status toggle is on)
- Check that the trigger condition is actually being met on the case
- Review the Activity tab — if it shows runs, the automation did fire
Automation firing on unexpected cases?
- Check the trigger settings and any conditions applied
- Review Upcoming to see which cases are queued to trigger next
Draft not appearing in list?
- Open the Drafts tab — all in-progress and manually-drafted automations appear there
See Also
- Case History — Audit trail of individual case changes
- Auto Save — How draft automation builds are preserved
- Case Management — Case operations overview