SECOPS

Daily digest of new OAuth app grants

Each morning pulls the prior day's OAuth consent grants from your IdP, groups them by risk tier and publisher.

CategorySecOps
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionPull prior-day grants from IdP audit APIHTTP webhook
  • LogicScore, group, and rank by risk
  • ActionPost ranked digest to channelSlack
  • OutputArchive full grant set to dated pageNotionNotion

What it does

Produces one daily summary of every third-party OAuth app consented to in the last 24 hours. Instead of a stream of per-event pings, it batches grants, ranks them by scope risk, groups repeat publishers, and delivers a single scannable digest. High-risk grants float to the top with their consenting users named.

When to use it

Use this when real-time per-grant alerts are too noisy but you still want daily oversight of OAuth sprawl. Ideal for a security analyst who starts the day reviewing what new apps entered the environment and decides which deserve deeper investigation.

How it works

  1. 1A scheduled trigger fires once each morning.
  2. 2An action queries the IdP audit API for all consent grants in the prior 24-hour window.
  3. 3A logic step scores each grant by scope sensitivity, collapses duplicate publishers, and sorts the list high to low.
  4. 4The formatted digest is posted to Slack with risk-tier sections and counts.
  5. 5The final output writes the full grant set to a dated page so the digest stays archived and searchable.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect NotionPages, databases, comments.
  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.