CHATBOTS
Datadog Monitor History Recap in MS Teams
An engineer asks the bot about a Datadog monitor in Microsoft Teams and gets a recap of how often it has fired recently, its flakiness pattern.
How it runs
The automated pipeline, trigger to output.
- TriggerEngineer asks about a monitor in MS TeamsMicrosoft Teams
- ActionQuery monitor transition history over lookbackDatadog
- ActionPull deploy timestamps for the same periodGitHub
- LogicCompute frequency, flakiness, and deploy-correlation rate
- OutputReply with recap card and tuning recommendationMicrosoft Teams
What it does
Provides historical perspective on a Datadog monitor rather than just the current state. When someone asks about a monitor in Teams, the bot summarizes its firing history, flags whether it is chronically noisy, and reports how many past alerts coincided with deploys, helping teams decide whether to tune or trust it.
When to use it
Use it during alert reviews or when deciding whether a paging monitor deserves its severity. Ideal for teams on Microsoft Teams who want to separate signal from chronic noise before acting on a fire.
How it works
The operator asks about a monitor by name or ID in Microsoft Teams. The workflow queries the Datadog events and monitor history API for all transitions over a chosen lookback. It pulls GitHub deploy timestamps for the same period. A logic step computes fire frequency, average duration, and the share of alerts that occurred shortly after a deploy. The bot replies in Teams with a recap card: total fires, flakiness verdict, deploy-correlation rate, and a recommendation to keep, tune, or downgrade the monitor.
Set it up
What you configure once, before turning it on.
- 1Connect Microsoft TeamsChannels, chats, files.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Chatbots workflows
Discord Onboarding Completion to CRM Sync
The moment a member finishes Discord onboarding, captures their submitted profile answers, creates or updates a contact in HubSpot.
Discord FAQ-Gated Role Concierge
Greets each new Discord member in a private onboarding thread, walks them through required FAQ steps one at a time.
Discord FAQ Free-Text Answer Grader
When a member submits a free-text answer in their onboarding thread, an agent grades it against the canonical FAQ knowledge base, replies with targeted feedback.
Discord verify-button onboarding via web form webhook
Receives a completed external verification form by webhook, matches it to the Discord account, grants the verified role, and confirms back to the member in Discord.
Discord intro-gated role granting concierge
Watches your #introductions channel, uses AI to confirm a new member's intro is genuine and complete, then auto-assigns the verified Member role and welcomes them.
Daily Discord Digest of Repeated WAF False-Positive Reports
Each morning, scans logged Discord WAF reports in Postgres, groups them by the Cloudflare rule that keeps firing.
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.