Turn long RFP files into ready to share responses without manual typing. Sales teams can upload a document once and get a structured answer set in Google Docs, plus alerts in email and Slack when it is done.

Here is how it works. A webhook receives the RFP file along with an ID, title, and reply email. The workflow extracts text from the PDF, uses an AI model to find the questions, and converts them into a clean list. It creates a new Google Doc, adds metadata like the RFP ID and timestamp, then loops through each question. An OpenAI assistant answers each question with company context, and every question and answer pair is written into the document. When all questions are processed, Gmail sends a message to the requester and Slack posts an update to the team.

To set this up, you need Google Docs, Gmail, Slack, and OpenAI accounts and credentials. Provide the Google Drive folder ID where new files should live, and paste your OpenAI assistant or model details in the AI nodes. Map the webhook fields for id, title, reply_to, and the file upload. Expect major time savings on proposal work and fewer copy paste mistakes. Great fit for B2B teams that handle frequent vendor questionnaires or security reviews.

• Webhook intake collects RFP file, ID, title, and reply email in one request
• PDF text extraction prepares the document for AI processing
• AI output parser turns detected questions into a clean list for looping
• Split in batches processes each question one by one for better quality
• OpenAI assistant generates answers using uploaded company context
• Google Docs creation builds a new response document and adds metadata
• Automatic logging writes every question and answer into the document
• Gmail and Slack notifications alert the requester and the team when done

• Reduce manual work from 4 hours to 15 minutes per RFP
• Automate 80 percent of repetitive writing and formatting
• Eliminate up to 90 percent of copy paste errors in responses
• Handle 5 times more RFPs per week with the same team
• Connect Google Docs, Gmail, Slack, and OpenAI in one flow

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Google Docs, Gmail, Slack and OpenAI. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, double click the Google Docs node and create a new Google Docs OAuth2 credential. Follow the on screen steps and grant access to your Drive and Docs. Name the credential clearly, for example Google Docs RFP.
4. Open the Gmail node and create a new Gmail OAuth2 credential. Approve the requested scopes and save the credential with a clear name such as Gmail RFP Alerts.
5. Open the Slack node and create a new Slack credential. Authorize the workspace and select the bot or user that can post to the target channel.
6. Open the OpenAI nodes and create a new OpenAI API Key credential. Get the key from your OpenAI account API page and paste it into n8n. Save the credential with a clear name like OpenAI RFP.
7. Open the Webhook node and copy the production URL. Keep it private. Use a tool like Postman to send a test request that includes id, title, reply_to, and the PDF file in a form post.
8. Open the Set Variables node and confirm the fields map to the webhook body. Ensure doc title, filename, and timestamp expressions read values from the webhook.
9. Open the Google Docs Create node and paste your target Google Drive folder ID where response files should be created.
10. In the AI nodes, paste your assistant or model settings. If using an assistant, provide the assistant ID and make sure the company reference file is uploaded to that assistant.
11. In the Gmail node, set the To field to the webhook reply_to value. In the Slack node, select the target channel and edit the message text as needed.
12. Send a sample webhook request with a real PDF. Confirm a new Google Doc is created, metadata is added, questions are detected, answers are written, and both Gmail and Slack messages are sent.
13. Troubleshooting: If the file is not read, check the webhook form field names and that the file is sent as multipart form data. If answers fail, verify the OpenAI key or assistant ID. If Slack or Gmail fail, check credential scopes and channel or recipient settings.