IT OPS

Reclaim 60-day-idle SaaS seats with manager sign-off

Weekly, finds SaaS seats with no login for 60 days, DMs each user's manager in Slack for a keep-or-revoke decision, and deprovisions the seats they approve.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps7
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionFetch all seats + last-login via admin APIHTTP webhook
  • LogicKeep only seats idle 60+ days
  • ActionDM each manager Keep/Revoke in SlackSlack
  • LogicBranch on manager response
  • ActionDeprovision approved seats via APIHTTP webhook
  • OutputPost reclamation summary to IT-ops channelSlack

What it does

Every week this workflow pulls last-login data for a SaaS app, flags any seat idle for 60+ days, and asks the seat owner's manager to confirm before anything is removed. Approved seats are deprovisioned automatically; declined ones are left alone and logged.

When to use it

Run it when license spend is creeping up and you want a repeatable, audit-friendly way to recover seats without an admin manually chasing people. Best for tools that expose a last-active timestamp and a provisioning API.

How it works

  1. 1A weekly schedule fires the run.
  2. 2The flow calls the SaaS admin API over an HTTP webhook to fetch all seats with their last-login timestamps.
  3. 3A filter keeps only seats idle 60 days or more.
  4. 4For each idle seat, it sends the manager a Slack message with Keep / Revoke buttons.
  5. 5On a Revoke response, it calls the deprovisioning endpoint to release the seat.
  6. 6It posts a summary of reclaimed and retained seats to the IT-ops Slack 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.