IT OPS
Offboarding Google Drive Ownership Transfer and Handover
Before a leaver's Google account is suspended, transfer ownership of their Drive files to their manager, archive a copy.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled scan of pending-offboarding queue
- ActionRead leavers due for handover from PostgresPostgres
- ActionList all Drive files owned by the leaverGoogle Drive
- LogicSplit files into transfer vs archive-only by recency
- ActionReassign ownership to manager and export archive copyGoogle Drive
- OutputSend handover manifest to manager in SlackSlack
What it does
Protects institutional knowledge during offboarding. It finds every file the departing employee owns in Google Drive, reassigns ownership to a designated successor, archives a backup copy, and produces a handover manifest listing what moved where.
When to use it
Run this in the days before suspending a leaver's account, when you need to guarantee that no shared docs, sheets, or folders become inaccessible after the seat is reclaimed.
How it works
- 1A scheduled check reads pending offboardings from a Postgres queue keyed by the departure date.
- 2For each leaver, the flow lists all Drive files they own, including shared-drive items.
- 3A logic step splits files into active (transfer) and stale (archive only) buckets by last-modified date.
- 4Active files have ownership reassigned to the manager named in the offboarding record.
- 5A snapshot copy of everything is exported to an archive folder.
- 6The handover manifest — file names, new owners, archive location — is sent to the manager via Slack.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect Google DriveDocs, sheets, slides, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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.
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.
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.
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.
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.