IT OPS
Offboarding GitHub Access Revoke and Audit Trail
On an offboarding ticket, remove the leaver from all GitHub orgs, teams, and repos, then write an immutable audit record of exactly what access was revoked and when.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear offboarding issue moves to Revoke AccessLinear
- ActionEnumerate GitHub org, team, and repo access for handleGitHub
- LogicSnapshot current access as before-state
- ActionRemove all memberships, grants, and pending invitesGitHub
- ActionWrite before/after diff to Postgres audit tablePostgres
- OutputComment revocation summary on the Linear issueLinear
What it does
Focuses the offboarding sweep on source-control risk. It removes a departing engineer from every GitHub org, team, and repository they belonged to, captures the before/after state, and stores a tamper-evident audit row so security can later prove access was cut.
When to use it
Use it for any engineer or contractor leaving, especially when compliance requires documented proof that code and CI access was removed on the termination date.
How it works
- 1A Linear offboarding issue moving to "Revoke Access" triggers the run with the leaver's GitHub handle.
- 2The flow enumerates the user's current org memberships, team seats, and repo collaborator grants via the GitHub API.
- 3A logic step snapshots that access list as the "before" state.
- 4Each membership and collaborator grant is removed, and pending invitations are cancelled.
- 5The before/after diff is written to a Postgres audit table with a timestamp and the triggering ticket ID.
- 6A confirmation comment is posted back on the Linear issue summarizing what was revoked.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
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.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Monthly Wasted-License Cost Report
Aggregates inactive-seat data across all tracked SaaS apps each month, computes total reclaimable spend, and delivers a ranked cost report to leadership in Notion and Slack.
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.