IT OPS
Daily Digest: Intercom Outage Mentions vs Datadog Alert History
On a daily schedule, it tallies Intercom outage-themed conversations against Datadog alerts from the same period and posts a Teams trend digest flagging recurring complaints…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionPull + categorize 24h outage-themed Intercom convosIntercom
- ActionRetrieve 24h Datadog alerts and eventsDatadog
- LogicDiff reports vs alerts → find blind spots
- OutputPost ranked trend digest to TeamsMicrosoft Teams
What it does
Runs a daily reconciliation between what customers report and what monitoring catches. It counts outage-related Intercom conversations from the prior 24 hours, lines them up against Datadog's alert history, and posts a Microsoft Teams digest highlighting recurring customer pain that telemetry is silent on — your monitoring blind spots.
When to use it
When the same "it's slow" or "keeps timing out" reports trickle in daily but never breach a monitor. This surfaces under-instrumented services and chronic low-grade degradation before they become outages.
How it works
- 1A scheduled trigger fires once daily.
- 2An Intercom action pulls and categorizes the last 24h of outage-themed conversations by service and symptom.
- 3A Datadog action retrieves the same window's triggered alerts and events.
- 4A logic step diffs the two: matched (reports + alerts), unmatched-customer (reports, no alert = blind spot), unmatched-monitor (alert, no reports).
- 5A Microsoft Teams output posts the ranked digest, leading with the top blind-spot services.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect Microsoft TeamsChannels, chats, files.
- 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 IT Ops workflows
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Monthly Wasted-License Cost Report
Aggregates inactive-seat data across all tracked SaaS apps each month, computes total reclaimable spend, and delivers a ranked cost report to leadership in Notion and Slack.
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.