IT OPS

Instant Seat Revocation on Employee Offboarding Webhook

Listens for an HR offboarding webhook and immediately revokes the departing employee's SaaS seats across every connected app, then logs and announces the reclaimed licenses.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHR offboarding webhook receivedHTTP webhook
  • ActionLook up employee's active seats in inventoryPostgreSQLPostgres
  • LogicOrder revocations, hold legal/export seats
  • ActionRevoke clearable seats via provider webhookHTTP webhook
  • ActionMark seats reclaimed in inventoryPostgreSQLPostgres
  • OutputConfirm reclaim summary in SlackSlack

What it does

When your HRIS or identity provider fires an offboarding event, this workflow instantly looks up every SaaS seat tied to that employee in your license inventory and revokes each one through the relevant provider webhook. It closes the gap between someone leaving and their paid seats being freed, eliminating the lag where licenses sit idle but billed.

When to use it

Use it the moment you want offboarding to actually reclaim licenses in real time instead of waiting for a periodic sweep. Critical for security (cutting access fast) and cost (no orphaned paid seats).

How it works

  1. 1An HR/identity offboarding webhook triggers the workflow with the employee identifier.
  2. 2Postgres returns all active seats mapped to that employee across SaaS apps.
  3. 3A logic step orders revocations, holding any seat flagged for legal hold or data export.
  4. 4Each clearable seat is revoked via the provider's HTTP webhook.
  5. 5Revocations are written back to the inventory as reclaimed.
  6. 6A Slack message confirms the offboarding reclaim with the count and any held seats.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  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.