> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/workflow/date-triggers.md).

# Date triggers

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

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

### Available trigger

* Specific date: runs on the date and time you choose.
  * First run: the date of the first run, a time of day, and the timezone that time is in.
  * Repeat this workflow (optional): **Weekly**, on one or more days of the week, or **Monthly**, on a day of the month from 1 to 28.
  * Without repeat, the workflow runs once, on the first run date.
* Repeats start one week (Weekly) or one month (Monthly) after the first run, then run on the next selected day. For example, a first run on Monday with Monday and Wednesday selected skips that week's Wednesday: the next run is the following Monday.
* Each run happens at the same UTC time as the first run. Daylight saving time is not applied, so in a timezone that changes clocks the local time shifts by an hour for part of the year: a 9:00 Paris run set in summer runs at 8:00 in winter.

### 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.

### Actions you can run

* Create a new request
* Create a group
* Send a communication: email or Slack notification to an audience you filter on People data (department, location, legal entity...)
* Slack, when connected: post a message on a Slack channel, create a public channel
* [Custom actions](https://docs.siit.io/integrations/custom-integrations.md) that need no request or person

A date trigger has no conditions: the run is not tied to a request or a person. Target people through the audience of **Send a communication**.

### Common recipes

* Monthly updates
  * Trigger: Specific date, repeat Monthly on day 1, at 9:00
  * Actions: Send a communication to everyone, or create a request for the team that owns the update
* Weekly team reminder
  * Trigger: Specific date, repeat Weekly on Monday, at 9:00
  * Actions: Post a message on a Slack channel
* One-off maintenance
  * Trigger: Specific date, no repeat
  * Actions: Send a communication to the affected departments, create a request to track the work

### 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
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/workflow/date-triggers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
