AI AGENTS
Triage inbound vendor requests from the procurement inbox
Watches a shared procurement inbox, classifies each new vendor request by spend tier and data sensitivity.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email in procurement intake labelGmail
- ActionAgent extracts vendor, tool, owner, spend, data flags
- LogicBranch on spend tier and data sensitivity
- ActionCreate structured request in vendor-intake databaseNotion
- OutputPost triaged summary and route to reviewerSlack
What it does
Monitors the procurement intake inbox and turns every raw vendor email into a triaged, structured request. It extracts the vendor name, requested tool, business owner, estimated spend, and whether customer or employee data is involved, then decides who needs to act.
When to use it
When vendor requests arrive as freeform emails and someone has to manually read, categorize, and forward each one. Use it to enforce a consistent intake the moment a request lands, before it stalls in an inbox.
How it works
- 1A new message in the procurement label triggers the run.
- 2An agent reads the email body and any attachment text, extracting vendor, tool, owner, spend estimate, and data-sensitivity signals.
- 3A branch checks the result: spend over $25k or any sensitive-data flag is marked high-touch; everything else is routed as standard.
- 4The structured request is written to the vendor-intake Notion database with a status of New.
- 5A summary plus the Notion link is posted to the procurement Slack channel, @-mentioning the security reviewer only on high-touch requests.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect NotionPages, databases, comments.
- 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 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.