IT OPS

Idle SaaS Seat Reclamation Sweep with Slack Approval

Runs a nightly sweep over last-login telemetry, flags seats idle past your policy window, and posts a batched reclaim list to Slack for one-click approval before deprovisioning.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires the idle-seat sweep
  • ActionQuery seats with last_login past policy windowPostgreSQLPostgres
  • LogicExclude exempt roles and batch candidates
  • ActionPost reclaim batch to Slack for approvalSlack
  • ActionDeprovision approved seats via provider webhookHTTP webhook
  • OutputWrite reclaim audit record back to PostgresPostgreSQLPostgres

What it does

Each night this workflow scans your SaaS usage table for accounts whose last login is older than your idle-seat policy (for example 45 days), assembles the candidates into a single review batch, and posts them to a Slack channel where an IT admin approves or skips before any seat is actually revoked. Approved seats are deprovisioned via your SaaS provider's webhook and the audit trail is written back.

When to use it

Use it when license costs are creeping up and you want a recurring, human-gated reclamation process rather than ad-hoc cleanup. Good for orgs that need an approval step for compliance but don't want to review every seat manually.

How it works

  1. 1A nightly schedule fires the sweep.
  2. 2Postgres returns every seat whose last_login exceeds the idle threshold and is still marked active.
  3. 3A logic step filters out exempt roles (executives, service accounts) and groups the rest into one batch.
  4. 4The batch is posted to Slack with per-seat approve/skip controls.
  5. 5On approval, an HTTP webhook call to the SaaS provider deprovisions each confirmed seat.
  6. 6The reclaim outcome is written back to Postgres as the audit record.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect HTTP webhookTrigger any URL on agent actions.
  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.