IT OPS
Auto-revoke at the end of an employee's last working day
Triggered by a last-day calendar event, this workflow waits until end of day, then revokes Slack and GitHub access and emails the manager a completed offboarding checklist.
How it runs
The automated pipeline, trigger to output.
- TriggerLast-day calendar event endsGoogle Calendar
- LogicConfirm offboarding event and get email
- ActionDeactivate Slack accountSlack
- ActionRevoke GitHub org accessGitHub
- OutputEmail manager the completed checklistGmail
What it does
Ties access removal to the calendar. When an employee's last-day event ends, the workflow revokes their Slack and GitHub access automatically and sends the manager an email confirming the offboarding checklist is complete.
When to use it
Use it when departures are planned and you want access to expire precisely at end of last day, not earlier (which cuts off a working employee) and not later (which leaves a gap). Removes the need for anyone to remember to flip the switch.
How it works
- 1A Google Calendar last-day event ending triggers the run.
- 2A logic step confirms the event is tagged as an offboarding and extracts the employee email.
- 3Slack deactivates the account so the person loses access at day's end.
- 4GitHub removes them from org teams and revokes their seat.
- 5The workflow assembles a checklist of what was revoked and when.
- 6It emails the manager a completed offboarding summary via Gmail as the confirmation and record.
Set it up
What you configure once, before turning it on.
- 1Connect Google CalendarEvents, attendees, availability.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect GmailRead, draft, send, label.
- 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.