When a new document lands in a chosen Google Drive folder, the system reads it, writes a short summary, and logs the key details in Google Sheets. Teams use it to scan long reports fast and keep a single list of summaries. It fits content intake, research notes, and meeting recaps.

The flow starts with a Google Drive event for file created and checks the folder every minute. Google Docs pulls the full text using the file id. An OpenAI model produces a clear summary from that text, and can call a Wikipedia lookup or a quick calculator tool when needed. A Google Sheets step appends the summary with the document name, last editor name and email, and the time, so your sheet becomes the index of record.

Setup needs Google access and an OpenAI key, plus rights to the folder and the sheet. Expect faster reviews, fewer copy and paste mistakes, and a clean history of what was uploaded. It helps teams that collect many docs from different people and need quick takeaways. Configuration is simple and can be done with a service account or OAuth, and testing is as easy as dropping a file in the folder.

• Watches a specific Google Drive folder and captures each new file on creation.
• Uses Google Docs to fetch the full document text by file id.
• Generates a clear summary with an OpenAI model using a simple prompt.
• Provides optional Wikipedia and calculator tools for extra context and numbers.
• Appends a new row in Google Sheets with summary, document name, editor name, editor email, and time.
• Supports service account access for stable, permission based connections.

• Reduce manual review from 60 minutes to 3 minutes per document
• Streamline content tracking by placing all summaries in one live sheet
• Improve data accuracy by removing copy and paste errors
• Handle up to 10 times more documents without adding staff
• Connect Google Drive, Google Docs, OpenAI, and Google Sheets 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 Drive, Google Docs, Google Sheets, OpenAI and Wikipedia. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, double click the Google Drive Trigger node, click Create new credential, and follow the prompts. Use a Google service account or OAuth. If you use a service account, share the target Drive folder with the service account email.
4. Open the Google Drive Trigger node and set Event to file created. Choose the specific folder to watch and keep the polling interval set to every minute.
5. Double click the Google Docs node. In the credential dropdown, select the same Google credential. Set the Document URL field to the expression {{$json.id}} so it reads the file that triggered the flow.
6. Open the Generate Summary AI node. In the credential dropdown, click Create new credential for OpenAI and paste your API key from the OpenAI account page. Keep the model as GPT 4o mini or pick your preferred model. Review the prompt text for clarity.
7. Double click the Google Sheets node. Click Create new credential and connect your Google Sheets account with OAuth. Make sure the connected account can edit the target spreadsheet.
8. In the Google Sheets node, pick the spreadsheet and the sheet tab. Map columns to fields: set Name to the Drive last editor display name, Email to the editor email, and Summary to the AI output. Add document link or date fields if you want more context.
9. Save the workflow and run a test. Upload a sample document to the watched Drive folder. Check Executions in n8n and confirm a new row appears in your Google Sheet with the summary and metadata.
10. Troubleshoot if needed: if no row is added, verify folder sharing and sheet permissions. If the summary is empty, confirm the Google Docs node is returning content. If the trigger does not fire, check the folder id and polling settings. Also review OpenAI quota and model name.