How to Automate Google Drive to Notion Meeting Notes?
Description
New audio files in a chosen Google Drive folder turn into clear notes in Notion. Great for teams that record meetings, interviews, or training. Get fast summaries without typing.
A Drive trigger checks the folder every minute and grabs each new file. The file is downloaded, then sent to OpenAI for speech to text. A second OpenAI step builds a structured JSON summary with a title, key points, and date context. The Notion node creates a fresh page, adds a heading called Summary, and writes the result so the team can read and search it.
Setup needs access to Google Drive, an OpenAI API key, and a Notion workspace. Expect note taking time to drop from an hour to a few minutes per recording, with a steady format across pages. Useful for podcast recaps, sales call notes, and internal briefings where speed and consistency matter.
Tools Required
What this workflow does?
- Google Drive Trigger checks a specific folder every minute for new audio files
- Google Drive node downloads the uploaded file and stores it as binary data named data
- OpenAI audio transcribe converts speech to text from the downloaded file
- OpenAI chat step turns the transcript into structured JSON with title and summary
- Prompt adds the current date so summaries include clear time context
- Notion node creates a new page and writes the summary under a clear heading
What are the benefits?
- Reduce manual note taking from 60 minutes to 5 minutes per recording
- Automate about 90 percent of the transcription and summary work
- Improve note consistency and cut copy paste errors by 80 percent
- Connect Google Drive and Notion seamlessly for one source of truth
- Handle up to 10 times more recordings without extra staff
How to set this up?
- 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.
- You'll need accounts with Google Drive, OpenAI and Notion. See the Tools Required section above for links to create accounts with these services.
- In the n8n Credentials Manager, create a Google Drive credential. If unsure, double click the Google Drive Trigger node, choose Credential to connect with, click Create new credential, then follow the on screen steps to sign in and allow access to the target folder.
- Create an OpenAI credential. In your OpenAI account, generate an API key on the API page, then in n8n add an OpenAI credential and paste the key. Name the credential clearly for future use.
- Set up Notion. In Notion, create an integration and connect it to your workspace. In n8n, create a Notion credential and then share the target database or parent page with the Notion integration so it can create pages.
- Open the Google Drive Trigger node and select the folder to watch. Keep the polling set to every minute or choose a different interval based on your volume.
- Open the Google Drive node and confirm the File ID expression is {{ $json.id }} and the Binary Property Name is data so the file passes correctly to the next step.
- In the OpenAI transcribe node, set the Binary Property to data and run a quick test with a short audio file to confirm the transcript appears in the field item.json.text.
- In the OpenAI summary node, keep the system message that asks for structured JSON. Verify that the output contains audioContentSummary.title and audioContentSummary.summary so the Notion node can read them.
- Configure the Notion node to create a new page in your chosen database or parent page. Map the Title field from the JSON and keep the Summary block content mapping as shown.
- Upload a small audio file to the watched Drive folder and wait one minute. Check the n8n execution log and confirm a new Notion page appears with the summary content.
- If the trigger does not run, confirm the correct folder is selected, the Google account has permission, and the poll interval is active. Re authenticate the Drive credential if needed.
- If the Notion page is empty or the title is null, validate that the OpenAI response is valid JSON. Adjust the system prompt to enforce the JSON shape and test again.
- Review several outputs and refine the prompt to add sections like action items or speaker names if needed for your team.
Need help or want to customize this?
Ask in the Free Futurise Community.
Similar Templates
These templates were sourced from publicly available materials across the web, including n8n’s official website, YouTube and public GitHub repositories. We have consolidated and categorized them for easy search and filtering, and supplemented them with links to integrations, step-by-step setup instructions, and personalized support in the Futurise community. Content in this library is provided for education, evaluation and internal use. Users are responsible for checking and complying with the license terms with the author of the templates before commercial use or redistribution.Where an original author was identified, attribution has been provided. Some templates did not include author information. If you know who created this template, please let us know so we can add the appropriate credit and reference link. If you are the author and would like this template removed from the library, email us at info@futurise.com and we will remove it promptly.
