Skip to main content
Workflow actions are the individual steps that execute when a workflow runs. Each action connects to a specific integration or Rootly capability. This page lists every available action grouped by category.
Actions that call an external tool need that integration connected first. The action still appears in the builder — it is flagged with a red Missing integration badge and the note “We will skip this task”.So a workflow that runs but skips a step is usually a missing integration rather than a broken workflow. Open the action in the builder and look for that badge before debugging conditions.
Many text fields support Liquid templating for dynamic values drawn from incident, alert, or on-call context. Selector fields (dropdowns, user pickers, etc.) do not accept Liquid.
Available actions depend on the workflow type (incident, alert, on-call, etc.). Actions for integrations you have not connected still appear — see the badge described above.
The Key fields column lists internal field names as they appear in the API and workflow schema. Labels in the UI may differ slightly (for example, workspace appears as Workspace in the form).

Slack


Microsoft Teams


Google Chat


Incident Management


On-Call & Paging


Project Management


Docs & Pages


Developer Tools


Observability


Meetings & Calendar


Notifications


AI

AI actions require the corresponding LLM integration to be configured in Settings → Integrations. The response from any AI action can be referenced in downstream actions using Liquid variables.

Utility

HTTP Client and Redis Client are also available as utility-style actions — see Developer Tools above.