IT OPS
On-call manual incident draft from intake form
An on-call engineer submits a short incident form; this drafts a severity-appropriate public status update, posts it to Slack for a second-set-of-eyes approval, then publishes.
How it runs
The automated pipeline, trigger to output.
- TriggerOn-call submits incident formHTTP webhook
- LogicMap severity to tone and cadence
- ActionDraft public status updateOpenAI
- ActionPost draft to Slack for approvalSlack
- OutputPublish update to status pageHTTP webhook
What it does
It takes a short manual intake submission from an on-call engineer (affected service, severity, one-line symptom) and drafts a polished public status update in tone matched to the chosen severity. A second engineer approves in Slack before it publishes, giving a fast path for incidents no monitor caught.
When to use it
Use it for the human-reported incidents that automated monitors miss, such as a customer-reported bug or a partner outage. The on-call gets a clean public update without writing copy, and the approval step keeps a second reviewer in the loop.
How it works
- 1An on-call engineer submits the incident intake form, triggering the workflow via webhook.
- 2A logic step maps the selected severity to the matching tone and required next-update cadence.
- 3An OpenAI step drafts the public status update from the form fields in that tone.
- 4The draft posts to Slack for a second engineer to approve or edit.
- 5On approval, 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 OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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.
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.
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.
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.
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.