> 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

Every workflow starts with a trigger. Siit offers four families, request, app access, people, and date, so you can react to work as it happens, to app access requests, to employee milestones, and to t

### Triggers: when an automation begins

Each workflow starts with a trigger. Siit provides four trigger families so you can react to work, app access, 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.

**App access triggers**

* Examples: App access requested, App access status changed (for example to Provisioned or Failed).
* Use these to follow up on an app access request once it is submitted, provisioned, rejected, or fails.
* See [App access triggers](https://docs.siit.io/workflow/app-access-triggers.md).

**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, run once or repeated every week or every month.
* Use for scheduled communication, reminders, or periodic maintenance.

### Starting a new workflow

**New** on the Workflows page opens a prompt: describe the workflow you want in plain language and Assist drafts it, then opens it for you to review. Four starters sit next to the box — **New laptop approval**, **Onboard a new hire**, **Monthly app review** and **Rejected app access** — and each one fills the prompt with a sentence you can edit before sending.

**Start from scratch**, under the box, opens the trigger picker instead and you build the workflow step by step. Admins without access to Assist go straight there.

Either way the workflow lands as a draft. See [**Workflow status**](https://docs.siit.io/workflow/triggers-overview#workflow-status) below.

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

### Workflow status

A workflow only starts new runs while it is **Live**.

* **Draft**: every new workflow starts here, whether you create it from the Workflows page, with Assist, or through the Siit MCP. A draft never runs. Click **Set live** on the workflow when it is ready.
* **Live**: the workflow runs each time its trigger fires.
* **Paused**: the workflow starts no new runs until you click **Set live** again. Runs already in progress, such as one waiting on an approval or a delay, may continue.
* **Archived**: the workflow is removed from your list. Pause a live workflow before you archive it.


---

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