AI AGENTS
Procurement Intake Agent: Draft RFQ from a Request Form
Turns a submitted procurement request into a structured, ready-to-send RFQ document and routes it to the requester's manager for approval before any vendor is contacted.
How it runs
The automated pipeline, trigger to output.
- TriggerProcurement request submittedHTTP webhook
- LogicValidate fields and check spend threshold
- ActionAgent drafts structured RFQ
- ActionWrite RFQ row to Coda trackerCoda
- OutputPost approval request to manager in SlackSlack
What it does
When an employee submits a procurement request (item, quantity, budget, needed-by date, justification), this agent reads the request, normalizes it, and drafts a complete Request for Quote. It writes the RFQ as a new row in a Coda procurement table and posts an approval prompt to the buyer's manager in Slack.
When to use it
Use it when your team files purchase requests through a form or webhook and you want every request converted into a consistent, audit-ready RFQ without a buyer hand-typing it. Ideal for ops teams standardizing intake before sourcing.
How it works
- 1A request payload arrives via webhook from your intake form.
- 2A logic step validates required fields and flags anything below the dollar threshold that can skip RFQ.
- 3The agent drafts the RFQ: scope, specs, quantity, delivery terms, and evaluation criteria.
- 4The draft is written as a structured row in the Coda procurement tracker.
- 5An approval message with Approve/Revise buttons is posted to the manager in Slack, linking back to the Coda row.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect CodaDocs, packs, automations.
- 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
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.