Actions library

The full menu of what a workflow can do: set status, priority and assignment, start approvals, send messages, add tags, call webhooks, and act in your connected third-party tools

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

• Create a group (create a named group holding 1 to 20 new requests in one step)

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

• Identity and access (Okta, Azure AD, Google Workspace, JumpCloud—varies by connection)

  • Activate/suspend user

  • Reset password

  • Add/remove from application

  • Add/remove from group

  • Revoke/restore sessions

  • De-provision user

  • Hand the requester a temporary password, an Okta temporary access code, or a computer's recovery key. These steps deliver the value to the requester themselves, so you don't add a message action after them — see Secret codes.

• Device management (Jamf, Iru, JumpCloud)

  • Send FileVault Recovery Key — reads the key the MDM escrowed for the requester's Mac and sends it to them privately.

  • Send Recovery Lock Password — same, for the Recovery Lock password of an Apple silicon Mac (Jamf and Iru).

  • Both steps fail before anything is read when the requester has no escrowed Mac, or more than one. Intune's BitLocker key is not available to workflows — see Secret codes.

• 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.

  • The actions you declare on a custom integration appear here too, once they carry a workflow input definition.

The actions a role can pick from depend on the integrations that role is granted — see Roles & permissions.

Action slugs

An action can carry a slug, a short lowercase name that identifies it inside its workflow. When an action has one, the workflow editor shows it in grey under the action's name, so you can tell two steps of the same kind apart at a glance.

Slugs are how later actions reference an earlier action's output, as {{actions.<slug>.<output>}}. They are set through the API, or by Assist when it builds a workflow for you, and they survive a workflow being rebuilt, which the internal action identifiers do not. See Variables & Secrets for how to use an action's output further down a workflow.