IT OPS
Daily sweep for dormant accounts of departed staff
Runs every morning, cross-checks an offboarding roster against live access in GitHub and Google Drive, and flags any account that should have been revoked but is still active.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule fires
- ActionRead departed-employee rosterAirtable
- ActionCheck lingering GitHub membershipGitHub
- ActionCheck active Google Drive accessGoogle Drive
- LogicKeep only still-active overdue accounts
- OutputPost exceptions to Slack ops channelSlack
What it does
Catches offboarding gaps. Each day it reads the list of employees marked as departed, checks whether they still have active GitHub org membership or Google Drive access, and posts any stragglers to a Slack channel for the IT team to clear.
When to use it
Use it as a safety net behind your real-time revocation. Manual offboarding misses things; this scheduled audit surfaces accounts that slipped through so nothing stays live past someone's last day.
How it works
- 1A daily schedule triggers the sweep each morning.
- 2The workflow pulls the roster of departed employees from an Airtable offboarding table.
- 3For each departed person, it checks GitHub for lingering org membership.
- 4It checks Google Drive for files still owned by or shared with that account.
- 5A branch keeps only accounts that are still active despite a past departure date.
- 6The exceptions are posted to a Slack ops channel with the account, the gap, and the days overdue.
Set it up
What you configure once, before turning it on.
- 1Connect AirtableBases, tables, views, automations.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect Google DriveDocs, sheets, slides, 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.