IT OPS

Revoke departed-employee app access on HRIS termination

When a termination record lands via webhook, this workflow revokes the employee's access across Slack, GitHub, and Google Drive, then writes an immutable audit record to Notion.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHRIS termination webhook receivedHTTP webhook
  • LogicConfirm event is a true termination
  • ActionDeactivate Slack accountSlack
  • ActionRemove from all GitHub org teamsGitHubGitHub
  • ActionTransfer Google Drive ownership to managerGoogle DriveGoogle Drive
  • OutputWrite revocation audit record to NotionNotionNotion

What it does

Turns an HRIS termination event into a full access sweep. It deactivates the employee's Slack account, removes them from all GitHub org teams, transfers their Google Drive ownership, and logs every revocation to a Notion audit page with timestamps.

When to use it

Use it the moment HR marks an employee as terminated and you want access killed within minutes, not at the next manual review. Ideal for teams that need a defensible audit trail for SOC 2 or ISO control evidence.

How it works

  1. 1A termination webhook fires with the employee's email and last day.
  2. 2A filter confirms the record is a real termination (not a transfer or leave) before any access is touched.
  3. 3Slack deactivates the user account by email.
  4. 4GitHub removes the user from every org team and revokes seat access.
  5. 5Google Drive reassigns file ownership to the employee's manager so nothing is orphaned.
  6. 6A Notion page logs each action, who triggered it, and the exact UTC time as the permanent audit record.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  4. 4
    Connect Google DriveDocs, sheets, slides, files.
  5. 5
    Connect NotionPages, databases, comments.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    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.