Example Webhook Request
Configured with Chain LLM, Extract From File, Gmail, Google Docs, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Transform
- Routing
- Files / media
- AI & models
- Messaging
- Trigger
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Get RFP Data | Transform | Extract From File | |
| Item List Output Parser | Transform | Output Parser Item List | See node parameters |
| For Each Question... | Routing | Loop Over Items | See node parameters |
| Set Variables | Transform | Edit Fields | See node parameters |
| Create new RFP Response Document | Files / media | Google Docs | See node parameters |
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Send Chat Notification | Messaging | Slack | See node parameters |
| Send Email Notification | Messaging | Gmail | See node parameters |
| Add Metadata to Response Doc | Files / media | Google Docs | update |
| Record Question & Answer in Response Doc | Files / media | Google Docs | update |
| Answer Question with Context | AI & models | Open Ai | assistant |
| Wait for Request | Trigger | Webhook | See node parameters |
| Extract Questions From RFP | AI & models | Chain LLM | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
gmailOAuth2googleDocsOAuth2ApiopenAiApislackApi
Workflow notes
1. API to Trigger Workflow
1. API to Trigger Workflow
Read more about using Webhooks
This workflow requires the user to submit the RFP document via an API request. It's a common pattern to use the webhook node for this purpose. Be sure to secure this webhook endpoint in production!
2. Create a new Doc to Capture Responses For RFP Questions
2. Create a new Doc to Capture Responses For RFP Questions
Read more about working with Google Docs
For each RFP we process, let's create its very own document to store the results. It will serve as a draft document for the RFP response.
3. Identifying Questions using AI
3. Identifying Questions using AI
Read more about Question & Answer Chain
Using the power of LLMs, we're able to extract the RFP questionnaire regardless of original formatting or layout. This allows AutoRFP to handle a wide range of RFPs without requiring explicit extraction rules for edge cases.
Additionally, We'll use the Input List Output Parser to return a list of questions for further processing.
4. Generating Question & Answer Pairs with AI
4. Generating Question & Answer Pairs with AI
Read more about using OpenAI Assistants in n8n
By preparing an OpenAI Assistant with marketing material and sales documents about our company and business, we are able to use AI to answer RFP questions with the accurate and relevant context. Potentially allowing sales teams to increase the number of RFPs they can reply to.
This portion of the workflow loops through and answers each question individually for better answers. We can record the Question and Answer pairings to the RFP response document we created earlier.
Try It Out!
Try It Out!
This workflow does the following:
- Receives a RFP document via webhook
- Creates a new RFP response document via Google Docs
- Uses LLMs to extract the questions from the RFP document into a questions list
- Loops through each question and uses an OpenAI Assistant to generate an answer. Saving each answer into the response document.
- Once complete, sends a gmail and slack notification to the team.
📃Example Documents To run this workflow, you'll need to following 2 documents:
Need Help?
Join the Discord or ask in the Forum!
Happy Hacking!
5. Send Notification Once Completed
5. Send Notification Once Completed
Finally, we can use a number of ways to notify the sales team when the process is complete. Here, we've opted to send the requesting user an email with a link to the RFP response document.
Sticky Note6
🚨Required
- Use a tool such as Postman to send data to the webhook.
Sticky Note7
🚨Required You'll need to create an OpenAI Assistant to use this workflow.
- Sign up for OpenAI Dashboard if you haven't already.
- Create an OpenAI Assistant
- Upload the example company doc to the assistant.
The assistant will use the company doc to answer the questions.
Sticky Note8
🚨Required
- Update the email address to send to in Gmail Node.
- Update the channel and message for Slack.
Example Webhook Request
Example Webhook Request
curl --location 'https://<n8n_webhook_url>'
--form 'id="RFP001"'
--form 'title="BlueChip Travel and StarBus Web Services"'
--form 'reply_to="user@example.com"'
--form 'data=@"k9pnbALxX/RFP Questionnaire.pdf"'
Example Webhook Request
Example Webhook Request
Purpose and structure
This folder contains the Example Webhook Request workflow. Its executable nodes use chainLlm, extractFromFile, gmail, googleDocs, lmChatOpenAi, openAi, outputParserItemList, set, slack, splitInBatches, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Wait for Request
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Googledocs/0524_Googledocs_Webhook_Create_Webhook.json MIT; preserve source notices.