Turn meeting transcripts into action without busy work. After a Google Meet ends, the flow reads the transcript, decides if a follow up is needed, then books a new Google Calendar event and adds the right people. It suits sales, customer success, and internal teams that want fast, clear next steps.

Here is how it runs. A manual or tool trigger loads the original calendar event to grab the meeting code. It calls the Google Meet API to find the transcript, downloads it from Google Drive, and converts it to PDF for reading. The text is sent to an AI model with strict output rules. An AI Agent then chooses if a follow up meeting is needed and passes only the details to a custom tool. A router creates the event in Google Calendar, splits the attendee list, and updates the invite for each person. A fallback path returns a clear error if the tool route is missing.

To set it up, you need Google Calendar, Google Drive, Google Meet access to transcripts, and an OpenAI API key. Set your calendar ID and event ID, and confirm the meeting has a transcript in Drive. Results include fewer emails, faster booking, and consistent invites. Good fits include sales calls, onboarding sessions, and project handoffs.

• Manual run or call as a tool using Execute Workflow Trigger
• Load the original Google Calendar event to extract the meeting code
• Query Google Meet conference records and transcript endpoints with HTTP Request
• Download the transcript from Google Drive and convert the file to PDF
• Parse PDF text for analysis using a file extract node
• Use an OpenAI chat model with temperature set to zero for consistent output
• Apply a structured output parser to capture summary and action fields
• Let an AI Agent decide if a follow up is needed and pass only the required details
• Route actions with a switch and create the meeting in Google Calendar
• Split the attendee list and add each person to the invite automatically
• Return a clear response or a fallback message if the tool is not available

• Reduce manual scheduling from 20 minutes to 2 minutes per follow up
• Automate up to 90 percent of post meeting booking steps
• Improve invite accuracy by using one consistent attendee list
• Connect Google Meet, Google Drive, OpenAI and Google Calendar in one flow
• Support many meetings per day without extra staff time

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 Calendar, Google Drive, Google Meet and OpenAI. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create an OpenAI API Key credential. Get your key from your OpenAI account API page, paste it into n8n, and name the credential clearly.
4. Connect Google Calendar. Double click the Get Calendar Event or Create Calendar Event nodes, choose Credential to connect with, click Create new credential, and follow the on screen steps to grant Calendar read and write access.
5. Connect Google Drive. Double click the Get Transcript File node, create a new Google Drive credential, and allow Drive read access and file export.
6. Authorize Google Meet API access. Open the HTTP Request nodes named Get Meeting ConferenceRecords and Get Meeting Transcript Location, create a new Google OAuth2 credential, and approve the scopes your admin allows. If you see 403 errors, ask your admin to enable Meet transcript access.
7. Open the Get Calendar Event node and set your calendar ID and event ID values. Use the notes in the canvas as a guide for where to place each value.
8. Confirm the meeting has a transcript in your Google Drive. Only recorded meetings with transcription enabled will appear.
9. Open the AI Agent node and ensure the connected language model is the OpenAI chat model with temperature 0. Check the tool named Schedule Meeting is linked to the Execute Workflow Trigger and that the router expects the action meetings.create.
10. Verify date and time formats match yyyy-MM-dd and HH:mm:ss in the request body. Set your time zone in Google Calendar node options if needed.
11. Run a test with the manual trigger. Watch the execution map, then confirm a new event appears in your Google Calendar with the correct attendees.
12. Troubleshoot common issues. If no transcript is found, inspect the HTTP node outputs and check the filter on meeting code. If attendees are missing, confirm the list includes name and email and that your domain allows external invites.