IT OPS

Weekly Dormant SaaS Seat Sweep from BigQuery Usage Logs

Each week, queries BigQuery SSO and app usage logs to find seats with no activity past a threshold, then posts a ranked reclamation list to Slack for IT review.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionQuery BigQuery for seats idle past thresholdGoogle BigQueryBigQuery
  • LogicRank by cost and drop below savings floor
  • ActionBuild per-app dormancy summary
  • OutputPost ranked reclamation list to SlackSlack

What it does

Runs a scheduled BigQuery query against your aggregated SSO and SaaS usage logs to surface every seat that hasn't shown login or feature activity in the last N days. It scores each dormant seat by monthly cost and posts a ranked, app-by-app reclamation candidate list to a Slack channel so IT can act in one place.

When to use it

Use it when license spend is creeping up and you suspect paid seats are sitting idle. Ideal for IT operations teams that already centralize login and product-usage events in BigQuery and want a recurring, no-effort dormancy report instead of manual quarterly audits.

How it works

  1. 1A weekly schedule fires the workflow.
  2. 2BigQuery runs a query joining identity events with per-app last-activity timestamps, filtering to seats idle beyond the dormancy threshold.
  3. 3A logic step ranks results by estimated monthly cost and drops seats below a savings floor.
  4. 4A formatting action builds a per-app summary with seat counts and projected savings.
  5. 5Slack posts the ranked candidate list to the IT channel for review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  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.