IT OPS
Correlate a burst of alerts into one public incident draft
On a schedule, this groups the last few minutes of related Sentry and Datadog alerts into a single deduplicated incident, drafts one public update.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled run every few minutes
- ActionFetch recent Sentry issuesSentry
- ActionFetch active Datadog alertsDatadog
- LogicCorrelate by service + time, dedupe into one incident
- ActionDraft one consolidated public updateOpenAI
- OutputFile single draft in Notion approval queueNotion
What it does
During a real outage, monitoring tools fire dozens of alerts that all describe the same underlying problem. This workflow runs on a short interval, pulls recent alerts from Sentry and Datadog, clusters the ones that point at the same affected service, and produces a single plain-language public draft instead of a flood of near-duplicate updates. The result is filed in Notion for a comms owner to approve.
When to use it
Use it when alert noise makes one-alert-per-update workflows spam your approval channel and confuse customers. This batches the noise into one coherent customer-facing story per affected component.
How it works
- 1A scheduled trigger runs every few minutes.
- 2Action steps fetch recent unresolved Sentry issues and active Datadog alerts.
- 3A logic step correlates them by affected service and time window, collapsing duplicates into one incident candidate; if nothing correlates, the run ends.
- 4An LLM step drafts one consolidated public update describing the combined impact.
- 5The single draft is written to a Notion approval queue, linking every contributing alert for the reviewer.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect SentryErrors, performance, releases.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect NotionPages, databases, comments.
- 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 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.