# 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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.siit.io/workflow/date-triggers.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.