IT OPS

Shadow-IT OAuth Grant Discovery to Airtable Inventory

On a daily schedule, pulls every third-party OAuth app authorized against your identity provider.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionFetch all OAuth grants from IdP admin APICustom MCP server
  • LogicNormalize scopes and tag sensitivity
  • ActionUpsert each app into Airtable inventoryAirtableAirtable
  • OutputWrite run summary row with new-app countAirtableAirtable

What it does

Keeps a living inventory of every third-party OAuth application that employees have granted access to your Google Workspace or Microsoft 365 tenant. Each app, its scopes, and the count of users who authorized it land in one Airtable base you can sort, filter, and review.

When to use it

Run this when you have no central record of shadow-IT app connections and need a baseline before you can decide what to revoke. It is the discovery layer the rest of your OAuth-governance workflows build on.

How it works

  1. 1A daily schedule fires the run.
  2. 2A custom-MCP call queries your identity provider's admin API for all authorized third-party apps, their granted scopes, and per-app user counts.
  3. 3A logic step normalizes scope strings and computes a coarse sensitivity tag (read-only, read-write, full-mailbox/drive).
  4. 4An Airtable action upserts each app by client ID, updating scope and user-count fields and stamping a last-seen date.
  5. 5The final output writes a run summary row recording how many apps were new this cycle.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Custom MCP serverConnect any MCP-compatible tool you own.
  2. 2
    Connect AirtableBases, tables, views, automations.
  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.