> 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/triggers-overview.md).

# Triggers overview

### Triggers: when an automation begins 

Each workflow starts with a trigger. Siit provides three trigger families so you can react to work, people, and time.

**Request triggers**

* Examples: Request submitted, Request resolved, Requester message received, Admin message sent, Tag added, Request marked In progress/Waiting/Snoozed/Reopened, Snooze expired, SLA breached, Requester unresponsive.
* Use these to drive intake routing, approvals, escalations, and auto‑close flows.

**People triggers**

* Examples: Start date, End date, Work anniversary, Birthday, Probation period.
* Use these for onboarding/off boarding sequences and recurring employee touch points.

**Date triggers**

* Example: Specific date.
* Use for scheduled communication, reminders, or periodic maintenance.

### Conditions: target precisely 

Refine when a workflow should run using rich conditions. You can mix request data, requester attributes, and form answers.

* Request context: status, priority, channel, inbox, assignee, tags, service (“Associated to”), created/updated dates, SLA state, satisfaction rating.
* Requester attributes: department, manager, job title/level, location, employment type, and any IdP‑synced custom attributes.
* Form results: any field from the service form (e.g., target app = “Okta,” office = “Paris”).
* Combinators: AND/OR groups, equals/contains/one of, greater/less than for numbers and dates.