IT OPS
Scheduled Open-Incident Status Digest
On a fixed schedule, pulls all currently open Sentry issues above a severity floor, writes a single consolidated plain-language status digest.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires (e.g. every 30 min)
- ActionFetch open Sentry issues above floorSentry
- LogicGroup related, drop low-impact
- ActionCompose consolidated status digestOpenAI
- OutputPublish digest + mirror to SlackHTTP webhook
What it does
Produces a periodic rollup instead of one update per error. It gathers every open, customer-impacting Sentry issue, dedupes and groups them, and writes one coherent digest so the public page reflects the current overall health rather than a flood of individual entries.
When to use it
Use it during a noisy period or a broad degradation where many related errors are firing and per-issue posts would overwhelm customers. Also useful as a recurring health summary your support team can point to.
How it works
- 1A schedule trigger runs at your chosen cadence, for example every 30 minutes during an active event.
- 2The flow queries Sentry for all unresolved issues above a severity floor.
- 3A logic step groups related issues and drops anything below the customer-impact threshold.
- 4OpenAI composes a single plain-language digest with an overall status line and per-area notes.
- 5The digest publishes to the status page via HTTP webhook and is mirrored to a Slack incident thread.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 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 IT Ops workflows
Recurring Sensor Fault Root-Cause Investigator
On a schedule, an agent reviews recent Monday work orders and BigQuery telemetry to identify equipment with repeating faults, drafts a root-cause hypothesis with a recommended fix.
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.
Agentic Inactive-Seat Reclamation Review
An agent investigates each idle SaaS seat by correlating SSO login gaps with HR status and ticket history, classifies it as reclaim, hold, or escalate, and drafts a reasoned…
Reconcile SSO logins against expense spend to find unmanaged tools
Joins SSO usage data with expense/payment records in Snowflake to surface tools that are being used but not paid for, or paid for but never logged.
Approved-Seat Deprovision Execution
Fires when an IT approver confirms a seat for removal, then executes deprovisioning via the IdP API and logs the action to an audit table and a Linear cleanup ticket.
HVAC Anomaly Detection to Severity-Routed Work Orders
Ingests building HVAC telemetry via webhook, flags out-of-band temperature, pressure, or runtime readings.
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.