💡 Can't find your transcript?
Configured with Agent, Execute Workflow Trigger, Extract From File, Google Calendar, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- AI & models
- Web / API
- Files / media
- Trigger
- Transform
- Integration
- Routing
- Subworkflow
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| OpenAI Chat Model1 | AI & models | OpenAI Chat Model | See node parameters |
| Get Meeting ConferenceRecords | Web / API | HTTP Request | See node parameters |
| Get Meeting Transcript Location | Web / API | HTTP Request | See node parameters |
| Get Transcript File | Files / media | Google Drive | download |
| When clicking "Test workflow" | Trigger | Manual Trigger | See node parameters |
| PDF Loader | Transform | Extract From File | |
| Get Calendar Event | Integration | Google Calendar | get |
| Structured Output Parser | Transform | Output Parser Structured | See node parameters |
| Execute Workflow Trigger | Trigger | Execute Workflow Trigger | See node parameters |
| Response | Transform | Edit Fields | See node parameters |
| Edit Fields | Transform | Edit Fields | See node parameters |
| Fallback Response | Transform | Edit Fields | See node parameters |
| Actions Router | Routing | Switch | See node parameters |
| Get Attendees | Transform | Edit Fields | See node parameters |
| Attendees List | Transform | Split Out | See node parameters |
| Add Attendee to Invite | Integration | Google Calendar | update |
| Create Calendar Event1 | Integration | Google Calendar | See node parameters |
| Schedule Meeting | Subworkflow | Tool Workflow | See node parameters |
| AI Agent | AI & models | Agent | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleCalendarOAuth2ApigoogleDriveOAuth2ApigoogleOAuth2ApiopenAiApi
Workflow notes
4. This Tool Creates Calendar Events
4. This Tool Creates Calendar Events
This tool, given event details and a list of attendees, will create a new Google calendar event and add the attendees to it.
1. Retrieve Meeting Transcript
1. Retrieve Meeting Transcript
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.
2. Let AI Agent Carry Out Follow-Up Actions
2. Let AI Agent Carry Out Follow-Up Actions
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.
3: Using the Custom Workflow Tool
3: Using the Custom Workflow Tool
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.
Try It Out!
Try It Out!
This workflow does the following:
- Retrieves a meeting transcript
- Sends transcript to an AI Agent to parse and carry out follow up actions if necessary.
- If transcript mentions a follow up meeting is required, the AI Agent will call a tool to create the meeting.
- Additionally if able, the AI Agent will also assign attendees it thinks should attend the meeting.
Need Help?
Join the Discord or ask in the Forum!
Happy Hacking!
1. Get Calendar Event
1. Get Calendar Event
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.
Sticky Note1
🚨Required
- Set your calendar event ID here.
💡 Can't find your transcript?
💡 Can't find your transcript?
Only meetings which own and were recorded and had transcription enabled will be available.
Sticky Note8
🚨Required
- Set your calendar ID here.
💡 Can't find your transcript?
💡 Can't find your transcript?
Purpose and structure
This folder contains the 💡 Can't find your transcript? workflow. Its executable nodes use agent, executeWorkflowTrigger, extractFromFile, googleCalendar, googleDrive, httpRequest, lmChatOpenAi, manualTrigger, outputParserStructured, set, splitOut, switch, toolWorkflow. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking "Test workflow", Execute Workflow Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Splitout/0530_Splitout_GoogleCalendar_Create_Webhook.json MIT; preserve source notices.