IT OPS

Catch Subscriptions Paid for Departed Employees

Cross-references active Stripe subscriptions and SSO ownership in Snowflake against the HR active-roster.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionPull subscriptions and owners from StripeStripeStripe
  • ActionQuery active roster and SSO statusSnowflakeSnowflake
  • LogicFlag subscriptions with departed owners
  • ActionOpen offboarding taskmonday.com
  • OutputAlert IT-ops with recoverable spendSlack

What it does

Matches the owner of every active SaaS subscription against the current employee roster. When the spend owner or SSO account belongs to someone who has left, the subscription is flagged as orphaned and routed for cancellation or reassignment, so the company stops paying for unowned seats and closes a dormant access risk.

When to use it

Use when employee turnover means subscriptions outlive the people who bought them. It pairs naturally with offboarding: the formal HR process rarely catches every personally-expensed or self-signed-up tool.

How it works

  1. 1A weekly schedule triggers the run.
  2. 2An action pulls active subscriptions and their owner identities from Stripe.
  3. 3An action queries Snowflake for the current active-employee roster and SSO account status.
  4. 4A logic step flags subscriptions whose owner is no longer active.
  5. 5An action opens an offboarding task in Monday to cancel or reassign each orphaned tool.
  6. 6A final output alerts IT-ops in Slack with the list and total recoverable spend.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect StripeCustomers, subscriptions, payments.
  2. 2
    Connect SnowflakeWarehouses, queries, shares.
  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.