Turn a document in Google Drive into a focused chat assistant that answers customer or visitor questions. It is ideal for event FAQs, product guides, policy pages, or onboarding instructions where consistent answers matter.

Here is how it works. A manual run fetches a selected Google Drive file and converts it to PDF. The file is uploaded to OpenAI and used to build a dedicated assistant with a clear system prompt and knowledge retrieval turned on. A chat trigger exposes a simple chat endpoint. Incoming questions flow to the OpenAI Assistant node, which replies using only the uploaded content, so answers stay accurate and on brand.

You only need Google Drive and OpenAI accounts and the correct file ID. After setup, you can test the chat, verify answers, and update content by replacing the document and running the upload again. Expect faster responses, fewer tickets, and less time spent copy pasting answers. Good fits include event information desks, course FAQs, internal policy help, and product support pages.

• Google Drive file download with automatic conversion of Google Docs to PDF for consistent parsing.
• File upload to OpenAI with the assistants purpose so the file becomes the assistant knowledge base.
• Assistant creation with model choice, system prompt, and attached file for grounded answers.
• Chat Trigger endpoint that receives user messages and starts a chat session.
• OpenAI Assistant node that sends questions to the assistant and returns the answer.
• Manual test trigger for quick end to end checks during setup.

• Reduce manual FAQ work from 2 hours to 10 minutes by loading a single document to power the chat.
• Streamline first line question handling by up to 60 percent with a self serve chat fed by your document.
• Improve answer accuracy by up to 90 percent by using one approved source for replies.
• Connect Google Drive and OpenAI without custom code or complex APIs.
• Refresh content in minutes by updating the document and re running the upload.

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 Drive and OpenAI. See the Tools Required section above for links to create accounts with these services.
3. Open the Upload File to OpenAI node. In the Credential to connect with field, click Create new credential, name it clearly, then paste your OpenAI API key from your OpenAI account API page. Save the credential.
4. Open the Get File node. In the Credential to connect with field, click Create new credential for Google Drive, sign in with the Google account that owns the file, and grant access. Save the credential.
5. In the Get File node, set the File ID to your Google Doc ID and keep Google file conversion set to export as PDF. Execute the node to confirm the file downloads correctly.
6. Run the Upload File to OpenAI node. Confirm it returns a file id. If it fails, check file size limits and try again.
7. Open the Create new Assistant node. Enter a clear name, choose a suitable model, add a short system prompt, enable knowledge retrieval, and map the file id from the previous node. Execute and note the assistant id created.
8. Open the OpenAI Assistant node. If it points to an existing assistant id, replace it with the new id or connect data from the Create new Assistant node so messages go to the right assistant.
9. Open the Chat Trigger node. Click Test to open the chat view or copy the webhook URL. Send a question from your document and confirm you receive a grounded answer.
10. Validation: Ask one question that is in your document and one that is not. Confirm the assistant relies on the document and follows the system prompt for out of scope questions.
11. Troubleshooting: If Google Drive returns an error, check sharing permissions and make sure the account has access. If OpenAI upload fails, verify the API key and quotas. If replies ignore your doc, ensure knowledge retrieval is on and the correct file id is attached to the assistant.