Connect Slack to Datadog

Send a message to a public or private channel. See the documentation

Add an emoji reaction to a message. See the documentation

Add an emoji reaction to a message. Accepts a channel ID or channel name (resolved automatically). Use **Get Channel History** or **Search** to find the message timestamp. Emoji name should be without colons (e.g. thumbsup, fire, heart). See the documentation

Suspend the workflow until approved by a Slack message. See the documentation

Archive a channel. See the documentation

List files shared in a channel or across the workspace. Accepts a channel ID or channel name (resolved automatically). Filter by file type (e.g. images, pdfs, snippets). Returns file metadata including name, type, size, and download URL. See the documentation

Configure custom blocks and send to a channel, group, or user. See the documentation.

Create a new channel. See the documentation

Create a reminder. See the documentation

Delete a file. See the documentation

Delete a message. See the documentation

Edit an existing message. Accepts a channel ID or channel name (resolved automatically). Requires the message timestamp (ts) from **Get Channel History** or **Post Message**. You can only edit messages posted by the same token/user. See the documentation

Find a Slack message. See the documentation

Find a user by matching against their email. See the documentation

Find a user by their ID. Returns user profile information including name, email (requires users:read.email scope), timezone, and status. See the documentation

Retrieve details for a Slack channel by selecting it or providing an ID. See the documentation

Read the recent message history from a specific channel. Accepts a channel ID or channel name (resolved automatically). Use this when you want to see a channel's latest messages — unlike **Search** which finds messages by keyword. Returns messages with text, timestamps (ts), reactions, and user IDs. Message timestamps can be used with **Get Thread Replies**, **Edit Message**, and **Add Reaction**. See the documentation

Retrieve comprehensive context about the authenticated Slack member, combining auth.test, users.info, users.profile.get, and team.info payloads. Returns the user’s profile (name variants, email, locale, timezone, status, admin flags), raw auth test data, and workspace metadata (domain, enterprise info, icons). Ideal when you need to confirm which user token is active, tailor messages to their locale/timezone, or ground an LLM in the member’s role and workspace before executing other Slack actions. See Slack API docs.

Return information about a file. See the documentation

Retrieve all replies in a message thread. Accepts a channel ID or channel name (resolved automatically). Use **Get Channel History** or **Search** to find the parent message's timestamp (thread_ts). Returns the parent message followed by all replies in chronological order. See the documentation

Retrieve the authenticated user's identity and workspace context. Returns user ID, name, email, timezone, profile, and workspace metadata. Call this first in any session to establish who you are — other tools like **Search** and **List Channels** can then filter by your user ID. See the documentation

Invite a user to an existing channel. See the documentation

Remove a user from a conversation. See the documentation

Return a list of all channels in a workspace. See the documentation

Detect the Datadog region for the connected account. Call this FIRST before any other Datadog tool if you do not already know the region. Returns the region domain (e.g. datadoghq.com) which must be passed as the region parameter to **Search Logs**, **Search Monitors**, **Get Metric Data**, and all other Datadog tools. See the docs

Detect the Datadog region for the connected account by validating the API key against each regional endpoint. Use this to discover the correct region before calling other Datadog actions. See the docs

Query time-series metric data for analyzing trends and system performance. Query syntax: avg:system.cpu.user{*}, sum:requests.count{env:prod} by {host}, max:system.mem.used{service:web}. Both from and to are POSIX timestamps in seconds. Use **Search Metrics** first to discover available metric names. Use **Search Hosts** to find valid host tags for scoping. After finding anomalies, use **Search Logs** to investigate related entries. See the docs

Get a list of logs matching a filter query. Uses the GET endpoint with a higher rate limit (3600/hr vs 300/hr). See the docs

Post custom time-series metric data points to Datadog. Data appears in dashboards, monitors, and can be queried via **Get Metric Data**. Points: JSON object where keys are Unix timestamps (seconds) and values are numeric, e.g. {"1640995200": 1.0}. Use **Search Metrics** to verify a metric name exists, or post to a new name to create it. This is a WRITE operation that creates or appends data to a metric time series. See the docs

List and search Datadog dashboards. Returns dashboard IDs, titles, URLs, and metadata. Dashboard URL: https://app.{region}/dashboard/{id} where region comes from **Get Account Info**. Use alongside **Search Services** to find dashboards related to a specific service. See the docs

Search Datadog events: monitor state changes, deployment markers, error spikes, and infrastructure events. Filter by sources (e.g. nagios,docker), tags (e.g. env:prod,service:web), and priority (normal or low). Time range defaults to last 24h (POSIX timestamps in seconds). To investigate a monitor alert, use **Search Monitors** first, then search events for the relevant time range. Follow up with **Search Logs** for deeper investigation. See the docs

Search monitored infrastructure hosts. Filter by tag (env:production), name (host:web-01), or partial match. Sort by cpu, iowait, load, status, or apps. Host names from results can scope queries in **Get Metric Data** (e.g. avg:system.cpu.user{host:web-01}), filter logs in **Search Logs** (host:web-01), or filter metrics in **Search Metrics**. Max 1000 results. See the docs

Search Datadog incidents by state, severity, and metadata. Query syntax: state:active, state:resolved, severity:SEV-1. After finding an incident, investigate with: **Search Logs** for the incident time window, **Get Metric Data** for relevant metrics, **Search Events** for related monitor alerts, and **Search Services** for ownership info. See the docs

Search Datadog logs matching a query with support for facets and time ranges. Uses log search syntax: service:web-app status:error, @http.status_code:>=400, boolean operators (AND, OR, NOT), and wildcards. Set from to now-1h for recent logs. Use **Search Metrics** to discover metric names or **Search Hosts** to find host names for filtering. To investigate an incident, use **Search Incidents** first, then search logs for that time window and service. See the docs

Discovery tool: list available Datadog metric names, optionally filtered by host. Returns metric name strings (e.g. system.cpu.user, aws.ec2.cpuutilization) for use in **Get Metric Data** queries with the syntax aggregation:metric.name{tags}. Use **Search Hosts** to find valid host names for the host filter. See the docs

Search Datadog monitors (alerting rules) including status, thresholds, and conditions. Query syntax: tag:env:production, type:metric, status:Alert. Tags filter: comma-separated (e.g. env:prod,team:backend). After finding a monitor, use **Search Events** to see recent state changes, or **Get Metric Data** to query the underlying metric it tracks. Returns monitor ID, name, type, query, status, and tags. See the docs

List services from Datadog's Service Catalog with ownership, metadata, and team info. Use to discover service names for filtering in **Search Logs** (service:my-app) or finding monitors via **Search Monitors** (tag:service:my-app). Returns service definitions including links, docs, and on-call. See the docs