Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions content/en/integrations/guide/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@ cascade:
{{< nextlink href="integrations/guide/fips-integrations" tag=" fips" >}}FIPS Verified Agent Integrations{{< /nextlink >}}
{{< nextlink href="integrations/guide/microsoft_teams_troubleshooting" tag=" Microsoft Teams" >}}Troubleshooting Microsoft Teams{{< /nextlink >}}
{{< nextlink href="integrations/guide/microsoft_teams_migrate_legacy_connectors" tag=" Microsoft Teams" >}}Migrate from Office 365 Connectors in Microsoft Teams{{< /nextlink >}}
{{< nextlink href="integrations/guide/slack-actions" tag=" Slack" >}}Slack Actions for Incidents, On-Call, Monitors, Dashboards, Workflows, and Accounts{{< /nextlink >}}
{{< /header-list >}}

{{< header-list header="AWS guides" >}}
Expand Down
81 changes: 81 additions & 0 deletions content/en/integrations/guide/slack-actions.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
---
title: Slack Actions
description: "Use Slack actions to manage incidents, on-call, monitors, dashboards, workflows, and accounts directly from a Slack workspace with the Datadog app installed."
further_reading:
- link: "/integrations/slack/?tab=datadogforslack"
tag: "Documentation"
text: "Slack Integration"
---
## Overview

Slack actions are available in any Slack workspace with the Datadog App installed. Type `/dd` in the workspace to open an action tray listing all available actions. Alternatively, type the full command directly.

## Incidents

@estherk15 estherk15 Jul 21, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this guide supposed to be a singular reference for all commands? If so, should we be referencing out to other docs?
Is there a possibility for drift since we're documenting this in multiple places? For example

Commands listed here that I couldn't find documented elsewhere:

  • /dd in investigate ("Trigger Bits Investigation")
  • /dd shortcuts ("View Incident Actions") — the Incident Management doc documents the bare /datadog command as opening the action tray instead. Is /dd shortcuts an alias for that, or a separate command?

Commands missing from this guide that exist elsewhere:

  • /datadog incident test (declare a test incident)
  • /datadog task / /datadog task list (create/list incident tasks)

Possible description mismatch for /dd in private:
This guide says: "Archive the current channel, create a new private channel, and add all existing responders."
The Incident Management doc says: "Make the incident private (if private incidents are enabled)."

Region availability:
The Incident Management doc notes /datadog incident summary isn't available in gov/gov2 regions. Should the same caveat apply to /dd in summary here?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes! We want this guide to be the source of truth for all possible actions existing on the /dd command modal.

  • /dd shortcuts is a new command that we added to invoke the incident action tray. The bare /datadog command will now invoke the command modal, so we need a new way to be able to pull up the action tray.

Will update this doc so the other pages align.

Use the following commands for incidents navigation. All commands can use `/dd in` as an alias for `/dd incident`. For more details, see [Integrate Slack with Datadog Incident Management][2].

| Command | Description|
| ------------------ | ---------- |
| `/dd in` or `/dd incident` | Declare an incident.|
| `/dd in test` | Declare a test incident.|
| `/dd in update` or `/dd in edit`| Update the incident's title, state, severity, and attributes.|
| `/dd in responders`| Manage the incident's response team.|
| `/dd in investigate` | Trigger Bits Investigation. |
| `/dd in summary` | Generate the incident's summary with AI. Not available in Gov and Gov2 regions.|
| `/dd in notify` | Notify @-handles about the incident. |
| `/dd in list` | List open incidents.|
| `/dd in private`| Archive the current channel, create a private channel, and add all existing responders.|
| `/dd in public` | Make the incident and its timeline visible to anyone with incident-read permissions. |
| `/dd followup` | Create a new follow-up.|
| `/dd followup list` | List Incident Follow-ups.|
| `/dd task` | Create an incident task.|
| `/dd task list` | List incident tasks.|
| `/dd shortcuts` | View Incident Actions.|

## On-Call
Use the following commands for On-Call. For more details, see [On-Call Pages][3].

| Command | Description|
| ------------------ | ---------- |
| `/dd page` | Page an on-call team.|
| `/dd shifts`| See your upcoming on-call shifts.|
| `/dd override`| Request someone to cover an on-call shift. |

## Monitors
Use the following commands for Monitors. For more information on adding Slack to monitors, see [Monitor Notifications][4].

| Command | Description|
| ------------------ | ---------- |
| `/dd monitors` | List monitors that are currently alerting.|


## Dashboard
Use the following commands for [Dashboards][5].

| Command | Description|
| ------------------ | ---------- |
| `/dd dashboard` | Share a dashboard widget to this channel.|


## Workflows
Use the following commands for Workflows. For more information on using Slack in Workflows, see [Trigger a workflow][6].

| Command | Description|
| ------------------ | ---------- |
| `/dd workflow` | Run an automation workflow.|


## Accounts
Use the following commands for [account management][7].

| Command | Description|
| ------------------ | ---------- |
| `/dd accounts` | Manage your linked Datadog accounts. |


[1]: /integrations/slack/?tab=datadogforslack
[2]: /incident_response/incident_management/setup_and_configuration/integrations/slack/#slack-commands
[3]: /incident_response/on-call/pages/#through-slack
[4]: /monitors/notify/#notification-recipients
[5]: /dashboards/
[6]: /actions/workflows/trigger/#slack-triggers
[7]: /account_management/
Loading