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

# App access triggers

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

App access triggers start an automation from an app access request: when it is submitted, and each time its status changes. Use them to confirm access to the requester, close the request once access is granted, or alert IT when provisioning fails.

Every app access request belongs to a request, so the request actions of the workflow act on that request.

### Available triggers

You find them under the **Apps** tab when you create a workflow.

* App access requested: Fires when an app access request is submitted.
* App access status changed: Fires each time the app access request moves to a new status.

### When to use

* Confirmation: tell the requester their access is ready and resolve the request once it is provisioned.
* Failure handling: open a request for IT, add a note, or post in Slack when provisioning fails.
* Rejections: explain next steps to the requester when the access is rejected.
* Follow-up in your tools: call a webhook or a custom action when access is granted or removed.

### Conditions you can add

* App access: the app asked for and, under it, its roles. Leave roles empty to match every role of the app.
* Status (App access status changed only): the new status of the app access request, one or more of Incomplete, Waiting approval, Rejected, Waiting provisioning, Provisioned, Waiting deprovisioning, Deprovisioned, Failed, Cancelled, Expired.
* Request fields: service (Associated to), status, priority, inbox, assignee, tags...
* Requester attributes: department, location, manager, contract type, job title/level, legal entity...
* Service form answers: any field you added to the service form.

### Actions you can run

The same actions as a [request trigger](https://docs.siit.io/workflow/request-triggers.md), such as set status, quick reply, add a note, assign, create a request, external requests, Slack actions, and actions in your connected identity tools. [Custom actions](https://docs.siit.io/integrations/custom-integrations.md) that run on an app access request are offered too. See the [Actions library](https://docs.siit.io/workflow/actions-library.md).

The app access request details (app, role, business reason, status) are available as variables in your messages — see [Variables & Secrets](https://docs.siit.io/workflow/variables-and-secrets.md#application-access-request).

### Common workflows

* Close the request once access is provisioned
  * Trigger: App access status changed
  * Conditions: Status = Provisioned
  * Actions: Send quick reply telling the requester their access is ready, set resolution and close
* Open a ticket for IT when provisioning fails
  * Trigger: App access status changed
  * Conditions: Status = Failed
  * Actions: Create a request assigned to the IT inbox, add a note on the original request, post a message in the IT Slack channel
* Explain a rejection
  * Trigger: App access status changed
  * Conditions: Status = Rejected
  * Actions: Send quick reply with the alternatives available to the requester

### Best practices

* Scope each workflow to the apps it is meant for, so one app's follow-up never fires for another.
* Use Status = Failed rather than a request trigger to catch provisioning errors as soon as they happen.
* Add a tag ("access-provisioned") for reporting impact.


---

# 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/app-access-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.
