> 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.md). # Workflow - [Triggers overview](https://docs.siit.io/workflow/triggers-overview.md): 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 - [Request triggers](https://docs.siit.io/workflow/request-triggers.md): Request triggers start an automation when something happens on a request: submitted, resolved, replied to, tagged, snoozed, or SLA breached. The fastest way to remove manual steps - [App access triggers](https://docs.siit.io/workflow/app-access-triggers.md): App access triggers start an automation when an app access request is submitted or changes status: provisioned, rejected, failed, and more. Use them to close the loop on access requests - [People triggers](https://docs.siit.io/workflow/people-triggers.md): People triggers start automations from employee lifecycle dates: start date, end date, probation, work anniversary, and birthday. Ideal for orchestrating onboarding and offboarding across teams - [Date triggers](https://docs.siit.io/workflow/date-triggers.md): 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 - [Actions library](https://docs.siit.io/workflow/actions-library.md): The full menu of what a workflow can do: set status, priority and assignment, start approvals, send messages, add tags, call webhooks, and act in your connected third-party tools - [Variables & Secrets](https://docs.siit.io/workflow/variables-and-secrets.md): Store a value once and reference it from any workflow. Variables stay readable for your team; secrets encrypt at rest and are never returned by the API - [Branching & approvals](https://docs.siit.io/workflow/branching-and-approvals.md): Branches let one workflow split into different paths based on the request, the requester, or the time. Build HR versus IT or EU versus US scenarios without duplicating workflows --- # 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.md?ask=&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.