IT OPS

Open reclaim tasks when offboarded staff keep SSO seats

When an employee is marked Offboarded on a Monday board, it checks whether they still hold any active SaaS seats and auto-creates a revocation task per leftover license.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonday employee row status changesmonday.com
  • LogicKeep only rows set to Offboarded
  • ActionLook up remaining SSO seats for userHTTP webhook
  • LogicBranch if any active seats remain
  • ActionCreate per-seat revocation task on IT boardmonday.com
  • OutputNotify IT owner in SlackSlack

What it does

This workflow closes the gap between HR offboarding and IT license cleanup. The moment someone's status flips to Offboarded on your Monday HR board, it looks up that person against every SaaS seat roster and opens a tracked revocation task for each license they still occupy, so no paid seat lingers after a departure.

When to use it

Use it when departures are frequent and seats routinely get forgotten, leaving you paying for ex-employees. It turns offboarding into the trigger for license recovery instead of relying on a quarterly sweep.

How it works

  1. 1A Monday item-update event fires when an employee row changes status.
  2. 2A logic step filters to only rows whose status became Offboarded.
  3. 3An HTTP call to the SSO directory confirms which apps that user still has active seats in.
  4. 4A branch checks whether any leftover seats exist.
  5. 5For each remaining seat, a revocation task is created back on a Monday IT board with the app, owner, and cost prefilled.
  6. 6A Slack note tags the IT owner that reclaim tasks are waiting.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect monday.comVisual work management for teams.
  2. 2
    Connect HTTP webhookTrigger any URL on agent actions.
  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.