Google Meet transcript to notes and follow-up events

Google Meet transcript to notes and follow-up events

An n8n workflow you start by hand. It takes one Google Calendar event, finds the Google Meet call attached to it, downloads
the call's transcript from Google Drive and gives it to an OpenAI agent. The agent writes a summary, each person's main
points and the next steps. If the attendees agreed to meet again, it also books that meeting in your calendar and invites
them.

What is inside

• workflow.json: the workflow as n8n exports it, 19 nodes and 9 sticky notes. It holds no credential.
• README.md: these notes.

What we changed from the original copy

• Three nodes pointed at the author's own calendar by its ID (Get Calendar Event, Create Calendar Event1 and
  Add Attendee to Invite). Each now reads <YOUR_CALENDAR_ID>.
• Get Transcript File read the transcript's address from $json.docsDestination.document. Google's reference for the
  Meet API says the transcript list answers with a transcripts array, and that document holds a bare document ID.
  The file had neither right. It now reads $json.transcripts[0].docsDestination.document, and the Drive node takes it
  in ID mode, because n8n's source makes URL mode accept only a full docs.google.com or drive.google.com address. Both
  were read on 12 November 2026.
• The agent's prompt listed attendees by attendee.display_name. Google's calendar events carry displayName, so every
  name would have printed as undefined. It now reads attendee.displayName.

Before you start

• An n8n instance, on n8n Cloud or your own server.
• A Google account that organised a Google Meet call with transcription turned on, and the Google Calendar event the call
  was booked from.
• A Google Cloud project with the Google Meet REST API turned on, for a Google OAuth2 API credential.
• An OpenAI API key.

Set it up

1. In n8n, create a workflow, open its menu and choose Import from File. Pick workflow.json, then save it. The agent's
   scheduling tool calls this same workflow by its own ID, so it needs a saved copy.
2. Add a Google Calendar OAuth2 credential. Select it in Get Calendar Event, Create Calendar Event1 and
   Add Attendee to Invite.
3. In those same three nodes, replace <YOUR_CALENDAR_ID> with the ID of the calendar the events live in.
4. In Get Calendar Event, replace abc123 with the ID of the calendar event for the call.
5. Add a Google OAuth2 API credential with the scope https://www.googleapis.com/auth/meetings.space.readonly. Select it
   in Get Meeting ConferenceRecords and Get Meeting Transcript Location.
6. Add a Google Drive OAuth2 credential and select it in Get Transcript File.
7. Add an OpenAI credential and select it in OpenAI Chat Model1. Open the node and pick the model you want.
8. Press Test workflow.

How a run goes

1. When clicking "Test workflow" starts the run by hand.
2. Get Calendar Event reads the event whose ID you set.
3. Get Meeting ConferenceRecords asks the Meet API for the conference record whose meeting code matches the event's
   conferenceData.conferenceId.
4. Get Meeting Transcript Location lists the transcripts of the first record.
5. Get Transcript File downloads the first transcript's Google Doc from Drive as a PDF, and PDF Loader pulls its text
   out.
6. AI Agent is an OpenAI Functions agent. Its prompt holds the meeting's creator, its attendees, its start time and the
   transcript. It asks for a summary with the meeting's goals, each attendee's main points and every next step, or up to
   three suggestions if none were agreed. It also asks for any follow-up calendar events. Structured Output Parser
   holds the answer to four fields: summary, highlights, next_steps and meetings_created.
7. When the attendees asked for another meeting, the agent calls Schedule Meeting, a tool named
   create_calendar_event. It runs this workflow again from Execute Workflow Trigger with the route
   meetings.create.
8. Edit Fields parses the agent's request, and Actions Router sends the meetings.create route to
   Create Calendar Event1. Any other route goes to Fallback Response, which says the tool was not found.
9. Get Attendees and Attendees List split the attendees, Add Attendee to Invite adds each one to the new event, and
   Response hands the event back to the agent as text.

Change the look

• What the agent writes: the numbered instructions in AI Agent's prompt.
• Which actions it may take: the same prompt says only calendar events are allowed. A new tool also needs its own route
  in Actions Router.
• The shape of the answer: the JSON schema in Structured Output Parser.
• The model: OpenAI Chat Model1. The file sets no model and a temperature of 0.
• The meeting's source: Get Calendar Event fixes one event ID. Change it to read the latest event, or replace the node
  to pick a call another way.

Good to know

• Only a call you organised, with recording and transcription turned on, has a transcript. A call with none leaves
  Get Transcript File nothing to read, and the run stops there.
• The model facts below come from pages read on 12 November 2026.
• The Meet reference lists meetings.space.created and meetings.space.readonly as the scopes that open these two
  calls. The Drive download needs the Drive credential on top.
• The chat model sets no model. n8n's source gives this node version gpt-5-mini, and OpenAI's model page marks that
  model Deprecated and points new work to gpt-5.6-terra. Pick a model in the node before you run it.
• OpenAI's deprecations page gives 14 January 2027 as the shutdown date of gpt-4o, gpt-4o-mini, gpt-4.1 and
  gpt-4.1-mini, and names gpt-6-luna as their replacement.
• AI Agent is on version 1.5 with the OpenAI Functions agent type. In n8n's source, newer agent versions offer only the
  Tools agent.
• The prompt asks the agent to book any follow-up meeting the attendees suggested, and nothing waits for your review.
  Whatever a person says in the call can shape what the agent books and who it invites.
• The agent's instructions sit in the user message, since options leaves the system message at n8n's default.
• Dates and times for the new event come from the agent as text. Check the first events it creates against your time zone.
• Billing: OpenAI bills the agent's calls, each one holding the whole transcript.
• The transcript, the attendees' names and email addresses and the event's start time go to OpenAI. Google handles the
  calendar, Meet and Drive requests.
• The sticky notes keep the original's section titles and its links to n8n's documentation.