IT OPS
On-Call Manual Incident Intake to Status Page
An on-call engineer submits a short incident form via webhook; the flow enriches it with the linked Sentry issue, drafts a customer-ready update at the chosen severity.
How it runs
The automated pipeline, trigger to output.
- TriggerOn-call submits incident formHTTP webhook
- LogicIf Sentry link present, enrich
- ActionPull referenced Sentry issue detailsSentry
- ActionDraft update at chosen severityOpenAI
- OutputConfirm in Slack, then publishSlack
What it does
Gives on-call a fast manual path to publish a status update for incidents that automated alerts miss, such as a degraded third party or a partial outage only humans noticed. The engineer provides a few fields and the flow does the polished, plain-language writing.
When to use it
Use it when not every incident originates from a Sentry threshold alert and you still want consistent, on-brand public comms without writing them by hand under pressure. Pairs well with the automated Sentry drafter as the human-initiated companion.
How it works
- 1A webhook receives a structured form: title, affected area, chosen severity, and an optional Sentry issue link.
- 2If a Sentry issue is referenced, its details are pulled in for accurate context.
- 3OpenAI drafts a plain-language update matching the selected severity tier.
- 4The draft is posted to Slack for a quick confirm before going public.
- 5On confirmation, the update publishes to the status page via HTTP webhook.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SentryErrors, performance, releases.
- 3Connect OpenAIModels, embeddings, files.
- 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.