Block 1 - Google Drive Trigger
- Type / Role
- n8n-nodes-base.googleDriveTrigger - googleDriveTrigger
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Automated Meeting Recording Transcription & Minutes Distribution Workflow Managing meeting recordings manually—downloading audio, transcribing it, summarizing key points, saving documents, and noti...
n8n-nodes-base.googledrivetrigger, n8n-nodes-base.googledrive, @n8n/n8n-nodes-langchain.openai, n8n-nodes-base.stickynote, n8n-nodes-base.converttofile, n8n-nodes-base.httprequest
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Yuki Hirota.
Original n8n.io sourceManaging meeting recordings manually—downloading audio, transcribing it, summarizing key points, saving documents, and notifying the team—quickly becomes repetitive and inefficient. This workflow eliminates all of those manual steps by automatically detecting new audio files uploaded to a designated Google Drive folder, converting them into high-quality transcripts using OpenAI, summarizing them into structured meeting minutes, transforming the content into a text file, uploading it back to Google Drive, and finally notifying a Chatwork room with the completed summary. What used to take hours can now be completed automatically within minutes, ensuring consistency, accuracy, and faster information sharing.
This workflow is ideal for:
By leveraging an advanced Meeting Minutes Generation System—capable of key-point extraction, noise reduction, speaker/topic organization, and review support—this workflow ensures that every meeting is transformed into a clean, structured, and highly usable document.
When a new recording is uploaded to the designated Google Drive folder, the Google Drive Trigger immediately activates and begins processing.
The file is retrieved from Google Drive and prepared in binary format for accurate transcription.
The audio is sent to OpenAI’s transcription engine, producing a complete and highly accurate transcript of the meeting.
The transcript is processed by a specialized Meeting Minutes Generation System powered by a multi-step prompt.
Instead of using a fixed template, the system intelligently analyzes the transcription and automatically generates a professionally structured document using the following capabilities:
Because the system dynamically determines the optimal structure, the resulting minutes adapt to the content of each meeting rather than following a rigid set of categories.
If certain information cannot be derived from the transcript, the system will appropriately leave it out rather than forcing placeholder sections.
The structured minutes are converted into a .txt or .docx document, ready for submission or archival.
The completed meeting minutes are uploaded to a specific Google Drive folder and saved using a timestamped filename.
A formatted notification—including the summarized content—is automatically posted to a Chatwork room, ensuring immediate team visibility.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Automate meeting transcription & minutes distribution with OpenAI and Google Drive |
|---|---|
| Complexity | intermediate |
| Nodes | 13 |
| Categories | Document Extraction, Multimodal AI |
| Author | Yuki Hirota |
| Published | 14 Nov 2025 |
Use the JSON export at /data/workflows/10820/10820.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Automated Meeting Recording Transcription & Minutes Distribution Workflow Managing meeting recordings manually—downloading audio, transcribing it, summarizing key points, saving documents, and noti...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction, Multimodal AI use case.