AI AGENTS
Vendor Quote Inbox Agent: Parse Quote Emails into a Coda Table
Watches a procurement inbox for incoming vendor quote replies, extracts line items, unit prices, lead times, and validity dates, and files each quote against the matching RFQ.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email in procurement inboxGmail
- LogicConfirm it references an open RFQ
- ActionAgent extracts quote line items and terms
- ActionAppend parsed quote to CodaCoda
- OutputNotify sourcing channel in SlackSlack
What it does
This agent monitors a shared procurement Gmail inbox. When a vendor replies with a quote, it reads the email body and any attachment text, extracts pricing fields, matches the quote to an open RFQ by reference number, and appends a structured quote record to Coda.
When to use it
Use it once RFQs are out and quotes start trickling back as free-form emails. It eliminates the manual copy-paste of vendor pricing into your sourcing sheet and keeps every quote tied to the right request.
How it works
- 1A new email arrives in the procurement Gmail inbox (trigger).
- 2A logic step checks whether the message references a known RFQ number and is actually a quote, not a clarification.
- 3The agent extracts vendor name, line items, unit price, total, lead time, and quote validity.
- 4It appends the parsed quote as a row in the Coda quotes table, linked to the parent RFQ.
- 5A short summary is posted to the sourcing Slack channel so buyers see new quotes land.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 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.