AI AGENTS
Stale RFQ Follow-up Nudger
Runs on a daily schedule, finds RFQs in Coda with no supplier reply past their deadline.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionRead open RFQs from Coda trackerCoda
- LogicSelect overdue RFQs under follow-up cap
- ActionSend polite follow-up email to silent suppliersGmail
- OutputUpdate follow-up count and flag escalations in CodaCoda
What it does
Chases down suppliers who haven't responded to an RFQ. Each day it scans the Coda tracker for outstanding requests past their response deadline and sends a courteous reminder to the non-responders, so quotes don't quietly stall.
When to use it
Use it when RFQs frequently go unanswered and you want consistent, timely follow-ups without a buyer remembering to chase each supplier manually.
How it works
- 1A daily schedule fires the trigger.
- 2The flow reads the Coda tracker and selects RFQs whose status is still 'awaiting reply' past their due date.
- 3Logic counts how many follow-ups each supplier has already received and stops after the configured maximum.
- 4For each eligible supplier, an agent sends a brief, polite follow-up email via Gmail referencing the original RFQ.
- 5The follow-up count and last-nudged date are written back to Coda, and rows that hit the max are flagged for buyer escalation.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect GmailRead, draft, send, label.
- 3Connect OpenAIModels, embeddings, files.
- 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.