> 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/core-platform/images-and-media.md).

# Workflows

Automate routine requests with a visual, no-code builder. Route, approve, provision, notify, and update requests, and orchestrate recurring processes like onboarding and offboarding

{% stepper %}
{% step %}

### Overview

Automate routine requests and free your team for work that requires expertise. Siit Workflows let you route, approve, provision, notify, and update requests using a visual, no-code builder. Use workflows to resolve straightforward requests instantly, accelerate complex resolutions, and orchestrate recurring processes like onboarding and offboarding.
{% endstep %}

{% step %}

### The table view

The workflow table is your control room. It lists every automation with status, trigger, category, ownership, and activity.

* Status chips: Live, Paused, Draft. Open a workflow and use Set live or Pause as you test and roll out safely.
* Filters and search: filter by status, trigger type, category, and created by. Sort by Last updated to find recent changes.
* Categories: group related workflows (IT Access, HR, Security). Categories can also be used in roles & permissions to limit who can view or edit a set of workflows.
* Activity: see “Total enrolled” to understand how often a workflow runs.
* Manage categories and create new workflows from the toolbar.
* Run History :
  * **Branch column** : each run row shows which branch the workflow took, so you can see at a glance which path ran.
  * **Clickable request ID** : click a request ID in the history to open that request in the current tab.
    {% endstep %}

{% step %}

### Build visually (no code)

Design the flow on a canvas. Read and manage complex automations at a glance.

* Drag‑and‑drop steps. Zoom, pan, and re‑order easily.
* Branching with Paths. Split the flow based on conditions (e.g., “If app = Okta → provision; else → create Jira ticket”).
* Draft → Live → Paused lifecycle using Set live and Pause buttons.
* Each step shows a summary (e.g., “Set status: New”). Open to edit details when needed.
  {% endstep %}

{% step %}

### Explore all the core features of requests management:

{% endstep %}
{% endstepper %}

{% content-ref url="/pages/tHhvtaXSTn4KFBVD3s4M" %}
[Triggers overview](https://docs.siit.io/workflow/triggers-overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/j0i39NN63GjwjxdmY3IX" %}
[Actions library](https://docs.siit.io/workflow/actions-library.md)
{% endcontent-ref %}

{% content-ref url="/pages/mZzWWaOfQdUcrhmaXiHr" %}
[Variables & Secrets](https://docs.siit.io/workflow/variables-and-secrets.md)
{% endcontent-ref %}

{% content-ref url="/pages/sFbxIlnts3aXpmbiFGoI" %}
[Branching & approvals](https://docs.siit.io/workflow/branching-and-approvals.md)
{% endcontent-ref %}

{% hint style="info" %}
You can also add images simply by copying and pasting them directly into the editor — and GitBook will automatically add it to your file manager.
{% endhint %}


---

# 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/core-platform/images-and-media.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.
