IT OPS
Agent-driven full access discovery and revocation
An agent investigates everywhere a departed employee still has access across connected systems, decides what to revoke versus reassign, executes the changes.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator starts offboarding for an employee
- ActionMap GitHub access and ownershipGitHub
- ActionDiscover Google Drive footprintGoogle Drive
- LogicDecide revoke vs reassign per item
- ActionDeactivate Slack accountSlack
- OutputWrite offboarding report to NotionNotion
What it does
Deploys an agent to do the judgment-heavy part of offboarding. Given a departed employee, it discovers their footprint across Slack, GitHub, and Google Drive, reasons about what to revoke outright versus reassign to a teammate, carries out the actions, and writes a narrative offboarding report.
When to use it
Use it for senior or cross-functional departures where access is tangled across owned repos, shared docs, and channel ownerships, and a flat checklist would miss context. The agent handles ambiguity a deterministic pipeline cannot.
How it works
- 1An operator starts the offboarding for a named employee.
- 2The agent queries GitHub to map repos, teams, and ownership the person holds.
- 3The agent queries Google Drive to find owned and shared documents.
- 4It reasons per item whether to revoke, transfer, or escalate, then executes revocations and ownership transfers.
- 5It deactivates the Slack account once dependencies are reassigned.
- 6It compiles a full offboarding report in Notion covering every decision and action for the audit trail.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect Google DriveDocs, sheets, slides, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect NotionPages, databases, comments.
- 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.