IT OPS
Publish an approved status update and broadcast it everywhere
When an on-call lead clicks Approve on a drafted update in Slack, this publishes it to the status page and simultaneously broadcasts the same wording to customers via email…
How it runs
The automated pipeline, trigger to output.
- TriggerApprover clicks Approve in SlackSlack
- LogicVerify approver + dedupe against last published
- ActionPublish update to status-page APIHTTP webhook
- ActionSend customer email broadcastGmail
- OutputPost public update across platformsSocial publishing
What it does
It closes the loop on the approval step. Once a human approves a drafted incident update in Slack, the workflow publishes the final text to your status page and pushes the identical wording out to every customer channel at once — so the status page, the customer email, and the public post never drift out of sync.
When to use it
Use it as the back half of an incident-comms pipeline: a separate workflow drafts the update, a person approves it, and this one handles consistent, simultaneous publication so no channel is forgotten or worded differently under pressure.
How it works
- 1An approval action in Slack (button click on the drafted update) triggers the workflow with the approved text and severity.
- 2A logic step confirms the payload came from an authorized approver and that the update isn't a duplicate of the last published state.
- 3An HTTP action posts the finalized update to the status-page provider's incidents API.
- 4In parallel, the same wording goes out as a customer email via Gmail and a public post via the multi-platform poster.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect GmailRead, draft, send, label.
- 4Connect Social publishingCross-post to X, LinkedIn, Instagram, TikTok, and 4 more in one call.
- 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.