AI AGENTS
RFP Drive Upload to Draft Response
Watches a Google Drive folder for new RFP documents, extracts requirements, researches each one, and generates a draft response document back into Drive.
How it runs
The automated pipeline, trigger to output.
- TriggerNew file in Drive RFP-Inbox folderGoogle Drive
- ActionRead file and split into requirementsGoogle Drive
- ActionResearch each requirementExa
- ActionDraft and assemble response documentOpenAI
- OutputSave draft Doc to Drafts subfolderGoogle Drive
What it does
Monitors a shared Google Drive folder where teammates drop incoming RFP files. When a new document lands, the workflow parses out individual requirements, researches each, and assembles a structured draft response as a new Google Doc in a Drafts subfolder.
When to use it
Use it when RFPs arrive as email attachments or vendor portal downloads that someone files into Drive, and you want a ready-to-edit response draft waiting before the kickoff meeting.
How it works
- 1A new file appears in the watched Drive RFP-Inbox folder, firing the trigger.
- 2The workflow reads the file contents and splits it into discrete requirement items.
- 3For each requirement, Exa runs targeted research for facts and proof points.
- 4OpenAI drafts a response paragraph per requirement and stitches them into one document with headings.
- 5The assembled draft is written as a new Google Doc in the Drafts folder, named to match the source RFP.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect ExaNeural search across the web.
- 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
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.