> 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/branching-and-approvals.md).

# Branching & approvals

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

### Workflow Branches

Branches let a single workflow split into different paths based on conditions about the request, the requester, time, or context. Use them to build multiple scenarios in one workflow (for example, handle HR vs. IT, US vs. EU, inside vs. outside office hours) without duplicating workflows.

#### What to expect

* One trigger, many outcomes: evaluate conditions and run different action sequences under each branch.
* Independent evaluation: each branch runs only if its condition is true. Multiple branches can run if several conditions match; make conditions mutually exclusive if you want only one path to fire.
* Mid‑flow decisions: insert a Branch anywhere in your action list to fork later steps based on updated fields or tags set earlier in the same workflow.
* Full audit: which branch(es) ran is logged in the request timeline.

#### What you can branch on

* Request fields: service, status, priority, inbox, tags, channel, source, SLA state, snooze/waiting, etc.
* Requester attributes: department, team, location, manager, contract type, seniority, employment status.
* Time and context: Office hours (within/outside), created date/time, day of week.
* Custom signals: your own tags or fields added earlier in the flow, or responses from webhooks.
* Outputs of earlier actions: anything a step before the branch produced, such as the request a `Create a request` step opened or the group a `Create a group` step built.

#### Branching on an earlier action's output

A branch placed after an action can read what that action returned. The condition picker groups those outputs by the action that produced them, so you pick `Create a new request > Request ID` rather than hunting through a flat list. The label stays short on the canvas and in the editor, and the full path — the branch it sits in, the action, and the output — is in the tooltip.

Outputs only appear for actions that run before the branch. Move a branch above an action and that action's outputs leave the picker.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2F1BhYN3OCH1vrIIMUxayw%2Fimage.png?alt=media&amp;token=ad7a1b7c-7220-410e-954d-d580e1b9a38b" alt=""><figcaption></figcaption></figure>

#### Typical use cases

* Language routing: if language = fr → reply with French template; if = en → English template.
* Access requests: if service = App Access and office = Madrid → set approver = local manager; else → app owner.
* After‑hours handling: if outside office hours and priority < P1 → auto‑reply and queue; if outside hours and P1 → notify on‑call.
* Region/team triage: if requester.department = Sales (EMEA) → HR‑EMEA inbox; if = Sales (AMER) → HR‑AMER inbox.
* Risk paths: if tag = “incident” → set priority High, add security followers; if tag = “FAQ” → auto‑reply and close when acknowledged.

***

## Approval requests

#### What is an approval request, and why is it important?

In a corporate environment, certain actions — such as accessing an app, ordering new hardware, or requesting time off — often require **prior validation**. This validation ensures that the right people are aware of the request, confirm its legitimacy, and approve it before resources are allocated or changes are made.

Approvals help businesses:

* Maintain control over costs and security
* Ensure alignment with internal policies
* Improve accountability across teams

Siit includes a powerful and flexible **Approval Request** feature that fits seamlessly into your automated workflows. Whether it’s granting app access, ordering equipment, or processing a specific employee request, Siit enables you to trigger **automated approvals** to the right people — at the right time.

#### How to set up an approval in your workflow?

The **Approval** is an action that can be added to any requests workflow via the "Select approver" action.

{% stepper %}
{% step %}

### Add an Approval action

Add an **Approval** action at the point where validation is needed.

![](https://content.gitbook.com/content/z9xmM8V3atukfr2XaElR/blobs/21BOros7fzSI3YGyB1AM/CleanShot%202025%2008%2005%20at%2016%2035%2010@2x%20png.png)

Once added, it will automatically present the two branches for the "approved" or the "rejected" option, allowing you to configure follow-up actions according to the choice made.

![](https://content.gitbook.com/content/z9xmM8V3atukfr2XaElR/blobs/sWWC3fjCnRqAiXtVfHEH/CleanShot%202025%2008%2005%20at%2016%2038%2003@2x%20png.png)

You can set up **single** or **multi-level** approval sequences.

> **Note.** An admin can cancel a pending approval directly from the request, whether it was sent manually or triggered by the workflow. Canceling stops the workflow at the approval step: neither the approved nor the rejected branch runs.
> {% endstep %}

{% step %}

### Define the approver

* Use dynamic fields like “Manager” or “App Owner” to automatically pull the right person from your data.
* Or assign a fixed employee as approver.
* Pick a team or an inbox instead of a named person. Everyone in the group is notified, and the first to respond decides for the group.

  <figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FavaMPnyoX4ZhCdtH6zrB%2Fimage.png?alt=media&amp;token=fbbba369-091d-4148-8494-2d99cc639f5c" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Set up reminders

Set up **reminders** to ensure follow-up if no action is taken. If the approval is not given after a certain time (from 1 day to several weeks), you can configure automatic reminders directly from the approval configuration to prevent the rest of the flow from proceeding.

![](https://content.gitbook.com/content/z9xmM8V3atukfr2XaElR/blobs/NYbJnO4pam1i8bRnMkfT/CleanShot%202025%2008%2005%20at%2016%2042%2049@2x%20png.png)
{% endstep %}
{% endstepper %}

#### How to approve?

Approvers are notified on Slack or Teams, then land directly on the request to decide. The **Approve** and **Reject** actions sit inline on the approver's own row — no separate approval screen to find.

* If the admin added a message for approvers, it shows above the actions, so the approver has the context before deciding.
* On a request with several approval rounds, each pending approver sees their own **Approve** / **Reject** next to their name, so there's no hunting for which decision is yours.
* The same experience is available in the Self-Service Portal.

![](https://content.gitbook.com/content/z9xmM8V3atukfr2XaElR/blobs/h4vQvucMnLK8q1DYXjX7/CleanShot%202025%2008%2005%20at%2016%2054%2002@2x%20png.png)

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FYsB6HF8F4R6jDtzwqHpq%2Fimage.png?alt=media&amp;token=6546651c-b90e-4635-bba4-cb3aea823b47" alt=""><figcaption></figcaption></figure>


---

# 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/branching-and-approvals.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.
