IT OPS

Build a renewal-ready seat utilization report from an upload

Triggered when you drop a vendor seat export into a Drive folder, it merges the file against SSO login data, classifies each seat as active, dormant, or never-used, and writes…

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerevent
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew seat export uploaded to Drive folderGoogle DriveGoogle Drive
  • ActionRead and parse the uploaded seat CSVGoogle DriveGoogle Drive
  • ActionEnrich users with SSO last-login datesCustom MCP server
  • LogicClassify each seat: active, dormant, never-used
  • ActionWrite utilization report back to DriveGoogle DriveGoogle Drive
  • OutputSlack the active-vs-paid ratio and renewal recommendationSlack

What it does

This workflow turns a raw vendor seat export into a clean utilization report your team can bring to a renewal negotiation. When a CSV lands in a watched Google Drive folder, it enriches every seat with SSO login signals and labels it active, dormant, or never-activated, then saves a formatted report alongside the source file.

When to use it

Use it ahead of a contract renewal when a vendor hands you a seat list and you need a defensible count of how many seats are genuinely in use. Great for one-off audits where you do not want a permanent integration.

How it works

  1. 1A new file in the watched Drive folder triggers the run.
  2. 2An action reads and parses the uploaded seat export.
  3. 3A custom MCP call retrieves SSO last-login dates for those users.
  4. 4A logic step buckets each seat into active, dormant, or never-used based on login recency.
  5. 5An action writes a formatted utilization report back to Drive next to the original.
  6. 6The output drops a Slack note with the active-vs-paid seat ratio and suggested seat count for renewal.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect Custom MCP serverConnect any MCP-compatible tool you own.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.