Skip to content

Docs / RivetMSP / Using the platform

Ticket automation rules

Triggers, conditions and actions that handle routine ticket work for you, with example rules.

Automation rules do routine ticket handling for you: set a priority, assign a technician, add a note, attach a worksheet, close a stale ticket, even run a script on a monitored device. Rules run in the background on every cron cycle, so cron must be enabled (see Cron Manager).

Find them under Administration > Ticket Automation. The page lists every rule with its trigger, conditions, actions and status. Use New Rule to add one, and Run Log to see what each rule actually did.

Triggers#

A rule starts from one of these events:

Trigger Runs when
Scheduled check On each cron cycle, against matching tickets
Ticket created A new ticket arrives
New RMM alert Your RMM reports a new alert
Asset offline A monitored device goes offline
Asset online A monitored device comes back

Conditions#

A rule can have several conditions, each a field, an operator and a value. Operators are equals, not equals, greater than, less than and contains.

Fields about the ticket:

  • Ticket age (hours) and hours since last reply
  • Priority, status, assigned technician and category
  • Subject and body text
  • Whether the SLA response or resolution has been breached

Fields about an RMM alert or device:

  • Alert severity and alert message
  • Asset, client, RMM integration and hostname

Actions#

A rule can take one or more actions:

Action What it does
Set priority Changes the ticket's priority
Assign to user Assigns the ticket to a technician
Set status Moves the ticket to a status
Add automation note Adds an internal note explaining what happened
AI triage (suggest) Suggests triage using the AI provider you configure in settings
Notify assigned tech Tells the assignee
Close ticket Closes it
Add worksheet from template Attaches a worksheet template (see Worksheets and forms)
Run RMM script Runs a script from your RMM on the device
Create ticket from alert Turns an RMM alert into a ticket
Acknowledge alert Acknowledges the alert in the RMM

The condition and action menus fill themselves from your live data, so categories, worksheet templates and RMM scripts appear by name.

Example rules#

  • Escalate stale tickets. Trigger: scheduled check. Condition: hours since last reply is greater than 48 and priority equals Low. Action: set priority to Medium and notify the assigned technician.
  • Onsite checklist. Trigger: ticket created. Condition: category equals On-Site. Action: add the "Onsite visit" worksheet template.
  • Alerts become tickets. Trigger: new RMM alert. Condition: severity equals Critical. Action: create ticket from alert.
  • Flag SLA breaches. Trigger: scheduled check. Condition: SLA response breached equals 1. Action: add a note and notify the assigned technician.

How often to run cron#

The page recommends running cron every 15 to 60 minutes for rules to feel timely. The Cron Manager lets you pick 5, 15 or 30 minutes, hourly or a custom schedule.

Tips#

  • Start with a rule that only adds a note, watch the Run Log for a day, then add the real action.
  • Rules are listed, and evaluated, in the order shown on the page.
  • Disabling a rule keeps it in the list without deleting it.

Event rules#

Alongside ticket automation rules, Event rules use a When, If, Then builder driven by the same 113-event catalog as webhooks. In RivetMSP a rule can create a ticket, send a webhook or notify technicians; 10 ready-made recipes get you started. The test drawer shows what a rule would do without any side effects, and run history records each firing. Open it from the Administration settings.

This guide is maintained by Rivet IT Ops. Found a mistake? Tell us. RivetMSP on GitHub