IT OPS

Offboarding-Triggered SaaS Seat Revocation Queue

When an HR webhook marks an employee as departed, instantly enumerates all their SaaS seats and opens a single consolidated deprovision approval with a Slack approve/deny prompt…

CategoryIT Ops
Enginesim
Difficultyadvanced
Triggerwebhook
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHR webhook fires on employee departureHTTP webhook
  • ActionLook up all SaaS seats for the user in PostgresPostgreSQLPostgres
  • LogicStop if no seats found, else continue
  • ActionCreate consolidated deprovision approval on Mondaymonday.com
  • ActionSend approve/deny prompt to IT Slack channelSlack
  • OutputOn approval, mark seats revoked in PostgresPostgreSQLPostgres

What it does

The moment HR fires a termination event, this workflow gathers every SaaS seat tied to the departing employee, bundles them into one consolidated deprovision approval, and drops an approve/deny prompt into the IT Slack channel. No more chasing scattered license cancellations days after someone leaves.

When to use it

Use it to close the offboarding gap, the days between a departure and the actual seat cleanup, where you keep paying for and exposing access on accounts that should be gone. Ideal when HR already emits a departure webhook.

How it works

  1. 1An HR webhook fires with the departing employee's identifier.
  2. 2Look up all SaaS seats and entitlements for that user in Postgres.
  3. 3Branch: if zero seats found, post a no-op note and stop.
  4. 4Create one consolidated deprovision approval record on the Monday board.
  5. 5Send an interactive approve/deny prompt to the IT Slack channel listing every seat and its monthly cost.
  6. 6On approval, mark the seats revoked in Postgres and confirm in the thread.

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 monday.comVisual work management for teams.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  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.