CHATBOTS
Datadog "Which Deploy Broke This?" Correlator
An engineer asks the bot which recent deploy likely caused a Datadog regression, and it correlates the metric's degradation timestamp against GitHub deploy events to name…
How it runs
The automated pipeline, trigger to output.
- TriggerEngineer asks which deploy caused a regressionSlack
- ActionQuery metric time series to find inflection pointDatadog
- ActionFetch deploy events and release tags in windowGitHub
- LogicScore and rank deploys by proximity and service match
- OutputReply with ranked culprits and linksSlack
What it does
Answers the single most common on-call question: which change broke the graph. The bot takes a Datadog monitor or metric and the time things went wrong, then mathematically aligns the degradation window with GitHub deploy markers to point at the deploy that best explains the regression.
When to use it
Use it when a metric clearly degraded but the cause is not obvious and multiple teams shipped recently. Best for services with frequent deploys where eyeballing the timeline is error-prone.
How it works
The operator messages the bot with a metric or monitor and an approximate "it got bad around" time. The workflow queries Datadog for the metric time series to pinpoint the actual inflection point. It then fetches GitHub deploy events and release tags spanning that window. A logic step scores each deploy by temporal proximity and whether it touched the alerting service, and filters out unrelated changes. The bot replies in Slack with a ranked culprit list, the confidence for each, and direct links to the suspect deploys and the metric graph.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 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.