> 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/guides/workflows/automations-and-workflows-use-cases.md). # Use cases Ready-made workflows for common IT and HR processes.


Automate App Access/Provisioning requests with workflows	Step by step article on how to set up a workflow for the app access requests.	Automate app access requests
Route requests by the requester's country	Send requests to the right team, approver, or inbox based on where the requester is located.	Route requests by country
Automate onboarding and offboarding with People Workflows	Automate onboarding and offboarding with People Workflows: target employees by condition, grant or revoke app access via Okta, JumpCloud or webhook, and notify stakeholders	Automate onboarding and offboarding
Creating Google Workspace Users via Siit Webhook	Seamlessly Provision Users with Siit Webhooks and the Google Directory API.	Create Google Workspace users with a webhook

--- # 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/guides/workflows/automations-and-workflows-use-cases.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.