IT OPS
Scheduled maintenance pre-notice from calendar
From a maintenance event on a shared calendar, this drafts an advance status-page notice with the window and expected impact, approves it in Slack, and schedules publication.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily scheduled calendar checkGoogle Calendar
- LogicSelect events within lead-time window
- ActionDraft maintenance pre-noticeOpenAI
- ActionPost draft to Slack for approvalSlack
- OutputPublish pre-notice to status pageHTTP webhook
What it does
It reads upcoming maintenance events from a Google Calendar and, a set lead time before each window, drafts a planned-maintenance status notice covering the schedule and expected impact. After Slack approval, the notice is published to the status page ahead of the work.
When to use it
Use it for planned work where customers deserve warning rather than a surprise. Drop the maintenance window on a calendar and let the workflow handle drafting and timely pre-notification, instead of someone remembering to post the night before.
How it works
- 1A scheduled check runs daily and reads maintenance events from the shared Google Calendar.
- 2A logic step selects events whose lead-time threshold has been reached and skips the rest.
- 3An OpenAI step drafts a planned-maintenance notice in an informative, low-urgency tone with the window and impact.
- 4The draft posts to Slack for approval.
- 5On approval, the pre-notice publishes to the status page via HTTP webhook.
Set it up
What you configure once, before turning it on.
- 1Connect Google CalendarEvents, attendees, availability.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 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.