AI AGENTS
Attachment PDF Bid Extractor
When a supplier emails a quote as a PDF attachment, the flow saves it to Google Drive, extracts the line-item pricing, and writes a structured bid record into Coda.
How it runs
The automated pipeline, trigger to output.
- TriggerEmail with quote PDF received in GmailGmail
- ActionSave attachment to Google Drive folderGoogle Drive
- ActionExtract line-item pricing from PDF with OpenAIOpenAI
- LogicValidate totals, flag low-confidence parses
- OutputWrite structured bid record to CodaCoda
What it does
Handles the common case where suppliers send quotes as PDF attachments rather than typed email bodies. It archives the file, reads the line items out of the document, and turns it into a structured Coda bid record you can compare and rank.
When to use it
Use it when your suppliers respond to RFQs with formal quote PDFs and you want the pricing captured and filed automatically instead of opening and transcribing each attachment.
How it works
- 1An email carrying a quote PDF attachment in Gmail fires the trigger.
- 2The attachment is saved to a dated folder in Google Drive for the audit record.
- 3OpenAI reads the document and extracts line items, unit prices, totals, currency, and validity date into structured fields.
- 4Logic validates the totals add up and flags any document it couldn't parse confidently for human review.
- 5The structured bid is written to the Coda tracker with a link back to the stored PDF.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect Google DriveDocs, sheets, slides, files.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect CodaDocs, packs, automations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.