HR & RECRUITING

Departing Employee Google Drive Ownership Transfer

On a scheduled sweep, this workflow finds files owned by employees marked as departed in monday, transfers ownership to their manager, and logs every reassignment.

CategoryHR & Recruiting
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily scheduled ownership sweep
  • ActionFetch departed employees and managers from mondaymonday.com
  • ActionSearch Drive for files owned by each employeeGoogle DriveGoogle Drive
  • LogicSkip employees with no owned files
  • ActionTransfer file ownership to managerGoogle DriveGoogle Drive
  • OutputSend reassignment report to HR and managersSlack

What it does

Prevents orphaned documents when someone leaves. It reads the list of departed employees and their managers from monday, searches Google Drive for files each former employee still owns, and transfers ownership of those files to the designated manager. Each transfer is recorded so nothing silently disappears when the account is finally deleted.

When to use it

Run this in the days after a departure, before the Google Workspace account is suspended. Ideal when knowledge work lives in shared docs and a deleted account would orphan critical files that the rest of the team still needs.

How it works

  1. 1A daily schedule triggers the sweep.
  2. 2The workflow fetches employees with a "Departed" status and their manager mapping from monday.
  3. 3For each one, it searches Google Drive for files they own.
  4. 4A logic step skips employees with no remaining owned files.
  5. 5It transfers ownership of each remaining file to the recorded manager in Google Drive.
  6. 6A reassignment report listing files moved per employee is delivered to HR and the receiving managers.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect monday.comVisual work management for teams.
  2. 2
    Connect Google DriveDocs, sheets, slides, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.