IT OPS

Orphan SaaS Charges: Flag Recurring Software Spend with No SSO Footprint

Scans the expense ledger for recurring SaaS charges that have zero matching SSO login activity, catching tools paid for outside identity governance, and queues each for review.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonthly schedule fires
  • ActionRead expense ledger and group recurring SaaS merchantsGoogle DriveGoogle Drive
  • ActionLook up matching auth events per merchant domain in DatadogDatadogDatadog
  • LogicKeep charges with zero SSO activity, minus sanctioned exceptions
  • ActionCreate 'No SSO footprint' Monday review itemsmonday.com
  • OutputPost orphan-spend alert to SlackSlack

What it does

Not every shadow app touches your identity provider — some are paid with a card and accessed with local logins, completely invisible to SSO. This workflow inverts the usual join: it finds recurring software charges in expenses that have no corresponding authentication events in Datadog, the riskiest blind spot, and files them for review.

When to use it

Run it monthly alongside the SSO-based discovery to catch what SSO can't see — local-account tools, personal-email signups expensed back, and vendors that bypass your IdP entirely.

How it works

  1. 1A monthly schedule starts the run.
  2. 2It reads the expense ledger CSV from Google Drive and groups line items into recurring SaaS merchants.
  3. 3It queries Datadog for any auth events tied to each merchant's domain over the same window.
  4. 4A logic step keeps only charges with zero matching SSO activity and excludes sanctioned exceptions.
  5. 5Each orphan charge becomes a Monday review item tagged "No SSO footprint" with amount and cadence.
  6. 6A Slack alert lists the orphan apps and total monthly spend at stake.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect DatadogMetrics, traces, log search.
  3. 3
    Connect monday.comVisual work management for teams.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.