AI & RAG
Weekly Service Baseline Drift Digest
On a weekly schedule, the bot compares each tracked service's key metrics against their established Datadog baselines, flags which ones have drifted.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionPull recent-week and 90-day series for each watchlist metric from DatadogDatadog
- LogicFlag metrics whose recent baseline diverges from the long-term baseline
- ActionLook up documented thresholds for flagged metrics in ConfluenceConfluence
- ActionCompose the drift digest with stale-threshold callouts (OpenAI)OpenAI
- OutputPost the weekly baseline drift digest to SlackSlack
What it does
Every week this workflow reviews a watchlist of service metrics, pulls each one's recent Datadog trend against its longer-term baseline, and identifies metrics whose normal range has quietly shifted. It cross-references the documented thresholds in Confluence runbooks, then posts a single Slack digest highlighting drift so the team can update alert thresholds and runbook expectations before the drift becomes an incident.
When to use it
Use it to keep alerting honest. Baselines decay as traffic patterns and deploys change; this catches the slow drift that makes monitors either too noisy or dangerously quiet.
How it works
- 1A weekly schedule trigger starts the run.
- 2Datadog returns recent-week and trailing-90-day series for every metric on the watchlist.
- 3A logic step flags metrics whose recent baseline diverges materially from the long-term one.
- 4For each flagged metric, Confluence is searched for the runbook's documented threshold.
- 5OpenAI writes a digest noting drift direction, magnitude, and whether the runbook threshold is now stale.
- 6The digest posts to the team's Slack channel with per-metric runbook citations.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI & RAG workflows
Coda-grounded sales answer bot with citations in Slack
Reps ask product, pricing, or competitive questions in Slack and get an answer drawn only from your Coda knowledge hub, with links to the exact docs and rows it pulled from.
Weekly knowledge-gap digest from unanswered rep questions
Each week, scans rep questions the answer bot couldn't ground in Coda, clusters the recurring gaps.
Pre-meeting prep brief grounded in Coda and CRM
Before each booked sales meeting, builds a one-page prep brief by combining the account's HubSpot context with grounded talking points and objection responses pulled from your…
Publish a Grounded API FAQ Page to Confluence Weekly
Each week, clusters the top unanswered or repeated API questions, generates spec-grounded answers with citations.
Detect Breaking API Changes from Spec Diffs and Alert Owners
Compares the new OpenAPI spec against the previous version on each GitLab merge, uses retrieval over the changelog to classify whether changes are breaking.
Re-Index API Specs on GitLab Merge to Keep the Answer Bot Fresh
Watches GitLab merges to your API repo, detects changed OpenAPI specs and changelog files, re-chunks and re-embeds only what changed.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
