# Actions library

### Actions: what workflows can do

Mix native request actions, notifications, webhooks, and third‑party integrations. Here’s the menu you’ll use most.

**Request**

* Set request status
* Set priority
* Assign to (team inbox or individual)
* Associate to service
* Start approval(s)
* Send quick reply (use a message template)
* Add a note (internal)
* Add/remove tags
* Add followers
* Set resolution and close
* Snooze / Pause or resume SLA

**Communication**

* Send a communication (email or portal notification)
* Post a message in a Slack channel (for swarms, incidents)
* DM requester or assignee via Slack/Teams

**Paths**

* Paths for conditional branches

**Webhook**

* Call external webhook with request payload

**Third-party applications** &#x20;

* Identity and access (Okta, Azure AD, Google Workspace—varies by connection)
  * Activate/suspend user
  * Reset password
  * Add/remove from application
  * Add/remove from group
  * Revoke/restore sessions
  * De-provision user
* Issue trackers
  * Jira: create issue; sync status/links
  * Jira Service Management: create linked ticket
  * Linear: create issue; sync status/links
* More integrations
  * Add additional tools as you connect them; actions appear automatically in the list.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.siit.io/workflow/actions-library.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
