HTTP and Slack: Datadog Monitor Digest Template

A daily scheduled workflow that pulls your open Datadog monitors and posts a clean digest of triggered alerts to Slack.

What It Builds

This template starts with a Schedule trigger that fires once a day. A Connector node uses the http connector to call the Datadog API (Miraxa researches that API and wires up the request for you, since Datadog does not have a native tile yet) and fetch every monitor currently in an alert or warn state. A second Connector node posts a formatted summary to your chosen slack channel, so your team sees the day's open alerts in one tidy message instead of a stream of pings.

The Prompt

Paste this into Spojit's Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow that runs every morning at 8am, calls the Datadog API to fetch all monitors currently in an alert or warn state, and posts a digest to the #ops Slack channel listing each monitor's name, status, and the affected service.

Connectors Used

Schedule trigger - runs the digest once per day on a cron you set.
http - calls the Datadog REST API to read open monitors (Miraxa connects to its API for you).
slack - posts the formatted digest to a channel.

Customize It

Change the run time in the prompt, swap #ops for your own channel, or narrow the pull to a specific tag or priority. You can also tell Miraxa to include only monitors above a given severity, or to add a count of total open alerts at the top of the message.

Tips

Add your Datadog API key and app key to the http connector node's headers when prompted.
Keep the Datadog read step in Direct mode so it runs the exact request with no AI cost.
Use the slack connection's bot token scope that allows posting to the target channel.