Automation Rules

Automation rules run repeatable work for you on a schedule or when specific data conditions are met. A rule combines three things:

1. A trigger (when to run)
2. Optional conditions (which records to match)
3. One or more actions (what to do)

Rules can target the entity types offered by your editor, including Devices, Companies, Compliance Controls, Planner Tasks, Users, Goals, Training, Tickets, Meetings, Survey Responses, Microsoft 365 Subscriptions, License Subscriptions, DNSimple Domains, CIPP findings and Onboarding. Most selectors are guided dropdowns, including PSA values like service boards, ticket categories, and issue types which populate from your connected PSA integration. A few fields (the Update Field field/value pair, Custom Email, ConnectWise issue-type IDs, and template bodies) are free-text inputs.

​

Accessing Automation

Navigate to Settings > Automation from the sidebar. The main page lists every rule in your tenant. Each row shows:

• Rule Name and description
• Trigger type badge (including Date Threshold, Scheduled and supported event triggers)
• Entity type badge (Device, Ticket, Meeting, etc.)
• Actions summary (either the single action label or “N actions”)
• Scope badge (All Companies or Specific)
• Enabled toggle to turn the rule on or off without deleting it

​

Row Actions

Hover over any rule row for the action menu: The enabled toggle on each row takes effect immediately. A disabled rule keeps its configuration and history but will not fire.

​

Permissions

Three permissions control access to Automation: Set these under Settings > Users & Roles on the role you want to grant access to. Users without Write or Manage permission open the wizard in read-only mode.

​

Execution Logs

Click Logs in the top-right of the rules page to open the execution history. Every rule run is logged with:

• Timestamp and rule name
• How many entities were matched
• Which actions ran and whether each succeeded
• Any error messages if an action failed

Logs are scoped by the company selector, so switching companies changes the visible execution history; it does not rewrite a rule’s saved scope.

​

AI Rule Designer

While editing or creating a rule, open the page’s AI Rule Designer from the assistant control available in your account. Describe what you want the rule to do in plain English, for example:

Remind account managers 30 days before each company’s warranty expires, and send them the device list.

The designer proposes a complete rule (trigger, conditions, actions, templates) as a diff against your current configuration. Review each section, accept the parts you want, and reject the rest. Useful for getting started quickly on complex rules or for generating email and planner templates.

​

Learning Path reminders

On Settings > Automation, choose Import > Learning Path reminders. The reminder rule defaults to Monday at 08:00 in your organization’s configured timezone. The import preview shows the exact timezone. Your browser’s timezone and the learner’s personal timezone do not change this rule’s default. The rule imports disabled. Review its schedule, conditions and email before enabling it. You can change the rule’s timezone in the editor. Reminders stop when the learner completes the path or the assignment is removed. Existing rules keep the schedule already saved on them.

​

How Rules Fire

• Date Threshold rules check every date on the chosen field and fire when it matches the configured window (for example, 30 days before warranty expiration). They are evaluated in the background; check execution logs for the actual run time.
• Scheduled rules run on a fixed frequency: every hour, every 6 hours, every 12 hours, daily, or weekly. You set the time of day for daily and weekly runs. Weekly rules include a weekday, time and timezone; review all three before enabling a rule.

Both trigger types respect the rule’s scope. A rule scoped to specific companies only evaluates records belonging to those companies.

​

Questions and troubleshooting

​

Next Steps