IT OPS

Weekly Idle SaaS Seat Reclaim Digest

Every Monday, cross-references SSO last-login telemetry against seat assignments to flag paid seats idle past your threshold.

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonday morning schedule fires
  • ActionQuery seat assignments + SSO last-login from PostgresPostgreSQLPostgres
  • LogicFilter to seats idle past threshold, rank by cost
  • LogicStop if no idle seats found
  • OutputPost ranked reclaim digest to SlackSlack

What it does

Each week this workflow finds paid SaaS seats nobody is actually using. It reads SSO last-login timestamps and seat-assignment records from your identity warehouse, compares them per app, and surfaces every license that has gone idle beyond your inactivity threshold (default 45 days). The result is a single ranked Slack digest showing wasted spend and one-click reclaim candidates.

When to use it

Run this when your SaaS spend is climbing and you suspect ghost seats — employees who churned, switched tools, or never onboarded but still hold a paid license. Ideal for IT and FinOps teams doing recurring license true-ups instead of annual scrambles.

How it works

  1. 1A Monday morning schedule fires the run.
  2. 2It queries Postgres for each seat's app, owner, cost, and SSO last-login date.
  3. 3A logic step keeps only seats whose last login predates the idle threshold and sorts them by monthly cost descending.
  4. 4If no idle seats are found, the run ends quietly.
  5. 5Otherwise it formats a digest with per-app totals and projected savings.
  6. 6The digest posts to your IT Slack channel with reclaim candidates listed for approval.

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
    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.