AI AGENTS
Slack Procurement Intake Triage Router
Staff post purchase requests in a Slack channel; the agent classifies urgency and category, asks for any missing detail in-thread, and routes the request to the right approver.
How it runs
The automated pipeline, trigger to output.
- TriggerNew message in procurement Slack channelSlack
- ActionClassify category, spend tier, and urgencyOpenAI
- LogicBranch on missing fields and reply in-threadSlack
- ActionRecord structured requestAirtable
- OutputRoute to matching approver with summarySlack
What it does
Lets employees request purchases by simply posting in a Slack channel. The agent reads each message, classifies the spend category and urgency, asks one clarifying question in-thread if something essential is missing, then routes the request to the correct approver.
When to use it
When procurement requests come in as casual Slack messages and get lost, or when routing to the right approver depends on category and dollar amount that requesters rarely state clearly.
How it works
- 1A new message in the #procurement-requests Slack channel triggers the agent.
- 2OpenAI classifies the message into category, estimated spend tier, and urgency, and detects any missing essential field.
- 3A logic step branches: if a field is missing, the agent replies in-thread asking for it and waits; if complete, it proceeds.
- 4The agent records the structured request in Airtable.
- 5Output: a routing message to the matching approver (by category and spend tier) with a summary and a link to the intake record.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect AirtableBases, tables, views, automations.
- 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
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.
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.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
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.
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.
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.
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.