CHATBOTS

Teams IT Bot: Departure-Triggered SaaS Seat Reclaim

When HR posts a departure to a webhook, the bot revokes the leaver's SaaS seats, reassigns reclaimed licenses, and reports the savings into a Teams channel.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHR departure webhook receivedHTTP webhook
  • LogicConfirm last day passed and resolve SaaS accounts
  • ActionRevoke leaver seats across providersSalesforce
  • ActionRecord reclaimed seats and cost in inventoryClickUpClickUp
  • OutputPost reclaim summary with savings to TeamsMicrosoft Teams

What it does

Reclaims SaaS licenses the moment someone leaves. An inbound HR webhook fires the workflow, which enumerates the departing employee's active seats across connected apps, revokes each one, marks the freed seats as available for reassignment, and summarizes recovered cost in Teams.

When to use it

Use it to stop paying for orphaned licenses and to close the security gap between an employee leaving and their access being cut. Best when offboarding events already emit a structured webhook from your HRIS.

How it works

  1. 1An HR system sends a departure webhook with the employee's email and last day.
  2. 2A logic step confirms the last day has passed and resolves the employee's SaaS accounts.
  3. 3The bot calls each provider's admin API to revoke or deactivate the leaver's seats.
  4. 4Reclaimed seats and their monthly cost are recorded in a ClickUp inventory list.
  5. 5The bot posts a reclaim summary, including monthly savings, to the IT Teams 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 SalesforceAccounts, opportunities, cases.
  3. 3
    Connect ClickUpDocs + tasks + chats in one workspace.
  4. 4
    Connect Microsoft TeamsChannels, chats, files.
  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.