AI automation case study
RFP Response Assistant
An n8n workflow that receives RFP attachments, validates the intake, reads only approved evidence, builds a cited draft, and stops for human review.
- Status
- Prototype
- Origin
- n8n
- Date
- 2026-08-23
RFP intake, approved-evidence, cited-draft, blocked-review, and human-review queue workflow
Open full-size imageProject proof
A closer look
Explore the interface and the decisions built into it. Open any capture at full size to read the details.
Earlier synthetic RFP validation capture with blocked, rejected, and human-approval branches
Open full-size imageProject proof
Watch the proof film
A short local film made from privacy-reviewed project captures. No contact records or client identities are shown.
Local privacy-reviewed proof film
Challenge
What needed to change
Tender responses can become slow and unreliable when requirements, source versions, citations, and missing evidence are tracked in separate documents.
System
How the system works
The workflow watches Gmail for an RFP attachment, validates the file and extracted requirements, reads only an approved Google Sheets evidence library, blocks missing support, creates a cited Google Drive draft, and logs the packet for human review.
- Input
- RFP email attachment and approved evidence library
- Output
- Cited Drive draft or a recorded blocked-review state
- Control
- Mandatory human review before any submission
Outcome
What is supported by the record
The public captures show both the supported-draft and blocked-review paths. Every successful draft remains awaiting human review; the workflow does not submit a tender automatically.
Screenshot
Current privacy-reviewed n8n canvas capture
Validation
Core paths tested with synthetic RFP fixtures
Tools
Connected tools and methods
- n8n
- Gmail
- Google Sheets
- Google Drive
- Google Chat
- Code nodes
- Shared error handler
Next step