IT OPS
Flag shadow SaaS from corporate card spend and open access reviews
Scans corporate-card and expense transactions in Snowflake for SaaS vendors that aren't on the approved-tools list.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery 30-day SaaS card spend from SnowflakeSnowflake
- LogicNormalize merchants and drop sanctioned vendors
- ActionOpen a Linear access-review issue per unknown toolLinear
- OutputPost flagged-tools digest to SlackSlack
What it does
This workflow finds unsanctioned SaaS purchases hiding inside expense data. It pulls recent card transactions from your Snowflake finance warehouse, matches merchant names against a sanctioned-vendor allowlist, and surfaces anything new or unapproved. Each genuinely new tool becomes a tracked access-review issue in Linear so security has a clear queue, and the team gets a single Slack summary instead of noise.
When to use it
Run it weekly or monthly when finance closes the books. Ideal for IT and security teams that want a recurring, low-effort way to catch tools employees bought on a card before they become a compliance gap or a renewal surprise.
How it works
- 1A weekly schedule kicks off the run.
- 2Snowflake returns card transactions from the last 30 days tagged as software or subscription spend.
- 3A logic step normalizes merchant strings and filters out vendors already on the sanctioned allowlist, keeping only unknown tools.
- 4For each remaining vendor, a Linear issue is created in the Security project with the merchant, amount, and buyer for an access review.
- 5A Slack digest lists every newly flagged tool and links to its Linear issue.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Monthly Wasted-License Cost Report
Aggregates inactive-seat data across all tracked SaaS apps each month, computes total reclaimable spend, and delivers a ranked cost report to leadership in Notion and Slack.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.