IT OPS

Reclaim SaaS seats for offboarded employees on HR signal

When an HR webhook reports a termination, finds every SaaS seat tied to that person, confirms revocation with the manager in Slack, and deprovisions on approval.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHR termination event hits webhookHTTP webhook
  • ActionList all seats for departing userHTTP webhook
  • LogicBranch on whether seats exist
  • ActionConfirm revocation with manager in SlackSlack
  • ActionDeprovision approved seats via APIHTTP webhook
  • OutputPost offboarding summary to IT-opsSlack

What it does

This event-driven workflow reacts to offboarding rather than waiting for an idle window. When HR fires a termination event, it looks up all SaaS seats owned by the departing employee, asks their manager to confirm cutoff timing in Slack, and deprovisions the approved seats so licenses do not linger after exit.

When to use it

Use it to close the gap between an employee leaving and their licenses being released — a common source of wasted spend and lingering access risk. Complements periodic idle-seat sweeps by catching departures immediately.

How it works

  1. 1An HR system posts a termination event to the inbound webhook trigger.
  2. 2The flow calls the SaaS admin API to list every seat assigned to that user's email.
  3. 3A branch checks whether seats were found; if none, it logs and exits.
  4. 4It sends the manager a Slack confirmation listing the seats and proposed revoke date.
  5. 5On approval, it calls the deprovision endpoint for each seat.
  6. 6It posts a confirmation summary to the IT-ops channel.

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
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.