IT OPS

Revoke seats still held by offboarded employees

Triggers on an HR offboarding event, immediately scans every connected SaaS tool for active seats under that person.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHR offboarding webhookHTTP webhook
  • ActionFind all active seats for departed userGoogle BigQueryBigQuery
  • LogicTag seats by access sensitivity
  • ActionNotify manager and ITOutlook
  • OutputOpen priority revoke ticket in ClickUpClickUpClickUp

What it does

Closes the dangerous gap between an employee leaving and their SaaS access actually being cut. When HR posts an offboarding event, this fans out across your tool inventory in BigQuery, finds every seat still active under the departed user, and raises an urgent deprovision ticket so no paid (or risky) access lingers.

When to use it

Use this whenever termination access cleanup is manual and slow. Critical for security and compliance reviews, and it doubles as cost recovery since orphaned seats keep billing.

How it works

  1. 1An HR offboarding webhook fires with the departed user's email.
  2. 2A BigQuery lookup returns every tool where that identity still holds an active seat.
  3. 3A logic step tags each seat by sensitivity (admin/data access first).
  4. 4The departing manager and IT get an Outlook notification confirming the revoke is underway.
  5. 5A single grouped ClickUp ticket is opened, priority set by the highest-sensitivity seat found, listing all tools to revoke.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  3. 3
    Connect OutlookMail, calendar, contacts.
  4. 4
    Connect ClickUpDocs + tasks + chats in one workspace.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.