Skip to main content
Replace scheduled “health check” meetings with a morning Slack digest. Every day at a time you pick, Devin queries Datadog for error rates, latency anomalies, and traffic trends across your services, distills the noise down to a digestible summary, and posts it to your team’s channel — so everyone starts the day on the same page.

Use this template

Open Daily Health Digest in Devin and create the automation with the default configuration. You can customize it before saving.
Looking for a hands-on walkthrough? See the step-by-step tutorial for Daily Health Digest.

​
What this automation does

The Daily Health Digest is a classic scheduled session automation. Devin uses the Datadog MCP to run the same morning-check queries an SRE would run manually: top error-rate endpoints, latency p95 regressions, unusual traffic spikes, and failing monitors. The output is a structured summary posted to Slack — scannable, linkable, and designed for a 30-second read.

​
How it works

Trigger: Schedule event — recurring
  • Event: schedule:recurring
    • Conditions:
      • rrule matches FREQ=DAILY;BYHOUR=8;BYMINUTE=0
What Devin does: Starts a session with full event context, executes the prompt below, and (optionally) notifies you on failure.

​
Prerequisites

  • MCP servers:

​
Example prompt

The template ships with this prompt. You can edit it after clicking Use template, or leave it as-is.

​
Setting it up

  1. Open Automations → Templates in Devin.
  2. Click Daily Health Digest. The create page opens with this template pre-filled.
  3. Connect any required integrations and install MCP servers if you haven’t already.
  4. Replace any placeholder values in the trigger conditions (for example, swap your-org/your-repo for your actual repo).
  5. Review the prompt and adjust it for your team’s language, conventions, and guardrails.
  6. Click Create automation.
Most automation templates include suggested ACU and invocation limits to bound cost during early rollout. Keep them as-is until you’re confident in the automation’s behavior, then raise them to fit your workload.

​
When to use this template

  • Replacing daily standup status updates with data-backed summaries
  • Giving non-SRE teams (product, support) a lightweight window into production health
  • Catching slow regressions before they become incidents
  • Building a historical archive of day-by-day production state

​
Customization ideas

  • Send to multiple channels (eng, leadership, per-service)
  • Swap the schedule to weekly or hourly depending on volume
  • Add comparison against the previous 7 or 30 days for trend detection
  • Attach a playbook that defines your team’s reporting format

​
See also