AI AGENTS
Flag duplicate and overlapping vendor requests before review
Checks each new vendor request against the existing approved-tools register and surfaces likely duplicates or functional overlaps so the team consolidates spend instead…
How it runs
The automated pipeline, trigger to output.
- TriggerNew row in vendor-intake tableAirtable
- ActionAgent matches against approved-tools registerAirtable
- LogicClassify as duplicate, overlap, or net-new
- ActionTag and link overlapping tool recordAirtable
- OutputRecommend consolidation or clear to proceedSlack
What it does
Guards against tool sprawl by comparing every incoming request to what the company already owns. It matches on vendor name and, more importantly, on what the tool actually does, catching cases where a new request overlaps an existing subscription under a different brand name.
When to use it
When teams keep requesting tools the company already pays for, and procurement only notices after the contract is signed. Use it to catch overlap at intake and redirect requesters to an existing license.
How it works
- 1A new row appearing in the vendor-intake Airtable triggers the run.
- 2An agent reads the request and queries the approved-tools register for name matches and capability overlap.
- 3A branch decides: clear duplicate, possible overlap, or net-new.
- 4For duplicate or overlap, the intake row is tagged and linked to the existing tool record.
- 5A Slack message goes to procurement summarizing the overlap and recommending consolidation, or confirming the request is net-new and clear to proceed.
Set it up
What you configure once, before turning it on.
- 1Connect AirtableBases, tables, views, automations.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.