n8n workflow template · 19 nodes · OpenAI
Actioning Your Meeting Next Steps using Transcripts and AI is a free n8n workflow template that runs when another workflow calls it and works with OpenAI, Google Drive and Google Calendar. It has 19 nodes, 4 of them AI nodes (OpenAI Chat Model, Structured Output Parser, Call n8n Workflow Tool and AI Agent). The notes inside the workflow say: “Join the Discord or ask in the Forum!” To run it, you add your own credentials for Google Calendar OAuth2, Google Drive OAuth2, Google OAuth2 and OpenAI API.
The text below comes from the sticky notes inside the workflow. We removed links, code samples and anything that looks like a key or token.
Join the Discord or ask in the Forum!
Read more about working with Google Calendar
In this demo, we've decided to go with google meet as transcripts are stored in the user google drive. First, we'll need to get the calendar event of which the google meet was attached. If the meet was not arranged through Google calendar, you may need to skip this step and just reference the transcripts in google drive directly.
Only meetings which own and were recorded and had transcription enabled will be available.
Read more about working with AI Agents
The big difference between Basic LLM chains and AI Agents is that AI agents are given the automony to perform actions. Provided the right tool exists, AI Agents can send emails, book flights and even order pizza! Here we're leaving it up to our agent to book any follow-up meetings after the call and invite all interested parties.
Read more about Workflow Triggers
One common implementation of tool use is to set them up as workflows which are intended triggered via other workflows. With this, we can either build a tool per workflow or for efficiency, take an API approach where multiple tools can exist behind a router (in this case our "switch" node).
Our AI agent will therefore only passing through the parameters of the request and won't have to learn/know how to intereact directly with the tools and services.
The text below comes from the sticky notes inside the workflow. We removed links, code samples and anything that looks like a key or token.
Read more about working with HTTP node
There's no built-in support for Google Meets transcript API however, we can solve this problem with the HTTP node. Note you may also need to setup a separate Google OAuth API Credential to obtain the required scopes.
This tool, given event details and a list of attendees, will create a new Google calendar event and add the attendees to it.
The 19 nodes in file order (sticky notes excluded). Branches and connections determine execution order in n8n:
Configure your own credentials after importing. Create each credential in n8n, then select it in the node.
Do you need somewhere to run it? Read our guide to self-hosted n8n.
We can adapt this workflow to your apps, data and process, then deploy and support it.
Contact Us