IT OPS
Manager-Approved Offboarding with Slack Gate
Starts on a manager's offboarding request, asks them to approve the revocation list in Slack, then sweeps the approved systems and reports back which seats were confirmed revoked.
How it runs
The automated pipeline, trigger to output.
- TriggerManager submits offboarding requestHTTP webhook
- ActionPost proposed revocation list for approvalSlack
- LogicGate: wait for approve vs. hold
- ActionRevoke approved seats and confirm eachGitHub
- ActionLog confirmed revocations to ledgerNotion
- OutputSend confirmation summary to managerSlack
What it does
Adds a human approval gate to access revocation. A manager submits an offboarding request, the workflow assembles the list of systems the employee can access, and posts that list to the manager in Slack for sign-off. Only after approval does it revoke each seat and confirm the removal, so revocation never runs on a wrong or premature request.
When to use it
Use it when offboarding requires explicit manager confirmation before access is cut — common for sensitive roles, planned transitions, or organizations where a mistaken revocation is costly.
How it works
- 1A manager submits a request via webhook with the employee's email.
- 2The flow gathers every system the employee currently has a seat in.
- 3It posts the proposed revocation list to the manager in Slack and waits for an approve/hold response.
- 4A logic gate blocks until approval; a hold pauses the run.
- 5On approval it revokes each approved seat and re-checks to confirm each one is inactive.
- 6A final confirmation summary is sent back to the manager and logged.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.