Date triggers

Date triggers run on a specific calendar date. Use them for scheduled communications, maintenance reminders, audits, and periodic housekeeping—no request or person event required.

Available trigger

• Specific date

When to use

• Monthly or quarterly reviews: send reminders or open tracker tickets on a set date.

• Hardware maintenance: nudge owners to update OS or schedule checks.

• Reporting and digests: send a summary of volume, SLA, and cost per request to leaders.

Conditions you can add

• Scope by object data so the run is targeted:

  • People: department, location, legal entity, employment type...

Common recipes

• Monthly updates

  • Trigger: Specific date (1st of month)

• Leadership digest

  • Trigger: Specific date (weekly)

  • Actions: Email execs a summary of created/resolved, SLA attainment, automation savings

Best practices

• Use tags like “scheduled-run” to track and report the impact of date‑based automations.

• Bundle communications: prefer one digest per audience over many single pings.

• Keep destructive actions (deprovision, resolve) behind conditions that are easy to audit.