Overview
The Google Meet integration automatically captures recordings from your Google Meet meetings and processes them into requirements. When you record a meeting with a client contact in attendance, Glossa automatically pulls the recording, transcribes it, and generates requirements—no manual upload needed.
How It Works
Automatic Recording Capture
Glossa monitors your Google Calendar for recorded meetings that include client contacts:
You record a Google Meet meeting (using Google Meet's native recording feature)
Glossa checks the participant list against your client contacts
If a participant's email matches a client contact email, Glossa captures the recording
The recording is processed and requirements are generated
The meeting is automatically associated with the appropriate project
Important: Glossa uses recordings only—there is no visible bot or notetaker that joins your meetings.
Meeting Matching
Recordings are matched to projects based on client contact emails:
Glossa compares meeting participant emails to client contacts in your projects
If a match is found with a project's client contacts, the recording goes to that project
If the contact is associated with multiple projects, the recording goes to a queue for manual assignment
Setting Up Google Meet Integration
Prerequisites
Before setting up:
You must have at least one project created
Your project must have a client with at least one contact that has an email address
You need a Google account with access to Google Meet
Setup Steps
Navigate to Integrations
Click Integrations in the main navigation
Find Google Meet in the list
Enable the Integration
Click Enable or toggle the Google Meet integration on
Connect Your Google Account
Click Connect
You'll be redirected to Google's authorization page
Sign in with your Google account (the one that hosts your meetings)
Grant Glossa the necessary permissions
Ensure Client Contacts Are Set Up
Go to your project
Verify that your client has contacts with email addresses
These email addresses must match the emails of meeting participants
Start Recording Meetings
Record your Google Meet meetings as usual
Glossa will automatically detect and process recordings with client contacts
Required Permissions
When connecting your Google account, Glossa requests permission to:
Access your Google Calendar (to find meetings)
Read meeting participant lists
Download meeting recordings
Note: Glossa cannot access meetings or recordings that you don't have permission to view.
Using the Integration
Recording Meetings
You must use Google Meet's built-in recording feature:
Start your Google Meet
Click the three dots menu (⋮) in the meeting
Select Record meeting
Conduct your meeting
Stop recording when done
Google automatically saves the recording to Google Drive
Important: Glossa only processes meetings that are actually recorded. If you don't record the meeting, Glossa won't capture it.
Which Meetings Get Processed
Glossa processes recordings that meet all of these criteria:
The meeting was recorded using Google Meet's recording feature
At least one participant email matches a client contact email in one of your projects
You have access to the recording in Google Drive
The meeting is not longer than 4 hours
Excluding Meetings from Processing
To prevent a meeting from being processed:
Option 1: Don't record it
Don't click "Record meeting" in Google Meet
No recording = Glossa doesn't process it
Option 2: Don't invite client contacts
If no participant emails match client contacts, Glossa won't process it
Useful for internal-only meetings
Note: There's no way to exclude a specific recorded meeting if it has client contacts. If you recorded it and clients were there, it will be processed.
Processing and Timing
Processing Time
After a meeting ends:
Recording availability: Google typically makes recordings available within a few minutes to an hour
Glossa processing: Once Glossa receives the recording, processing takes a few minutes
Total time: Expect requirements to appear within a few hours after the meeting ends
Factors affecting timing:
Meeting length (longer meetings take longer to process)
Google's recording processing time
Current processing queue
Maximum Meeting Length
Glossa can process meetings up to 4 hours long.
Meetings longer than 4 hours:
May fail to process
Contact support if you regularly have meetings exceeding this limit
Where Recordings Are Stored
Recordings are stored in two places:
Google Drive - Google automatically saves recordings to the meeting organizer's Drive
Glossa - A copy is stored in Glossa for processing and citation purposes
You can delete the recording from Google Drive without affecting Glossa's copy.
Manual Upload Option
If automatic capture doesn't work, you can manually upload recordings:
Download the Google Meet recording from Google Drive
Go to your Glossa project
Click Files → Upload
Select the recording file
Upload and wait for processing
When to use manual upload:
Automatic capture failed for some reason
You want to process a recording from before the integration was set up
The meeting wasn't on your calendar but you have the recording file
The meeting didn't include client contacts, but is relevant to the project
Project Assignment
Automatic Assignment
When a recording has participants matching client contacts:
Single project match:
If the client contact is only associated with one project
The recording automatically goes to that project
Requirements are generated in that project
Multiple project match:
If the client contact is associated with multiple projects
The recording goes to a manual assignment queue
A bell notification indicates that you need to review the queue
Manual Assignment from Queue
If a recording is in the queue:
You'll see a notification on the bottom left of your screen
Open the queue
View the recording details (participants, meeting title, date)
Select the appropriate project(s)
Confirm assignment
Glossa processes the recording for that project
Tip: Use descriptive meeting titles in Google Calendar to make queue assignment easier.
Troubleshooting
Recording wasn't captured automatically
Check these common issues:
Was the meeting recorded?
Glossa only processes recorded meetings
Verify the recording exists in Google Drive
Are client contacts set up correctly?
Go to Clients → [Your Client] → Contacts
Verify email addresses match meeting participants exactly
Check for typos in email addresses
Did the meeting happen recently?
Processing can take a few hours
Wait at least 4 hours after the meeting before troubleshooting
Is the integration still connected?
Go to Integrations
Verify Google Meet shows as "Connected"
Try disconnecting and reconnecting if needed
Was the meeting longer than 4 hours?
Meetings over 4 hours may not process
Consider breaking very long meetings into sessions
Recording is in the wrong project
If a recording was assigned to the wrong project:
Prevention:
Ensure client contacts are only associated with relevant projects
Use more specific client contacts for different project phases
Fix:
Currently, you cannot move a recording between projects
Consider uploading the recording manually to the correct project
Integration shows as disconnected
Possible causes:
You revoked Glossa's access in Google settings
Account password was changed
Solution:
Go to Integrations
Click Reconnect or Connect next to Google Meet
Re-authorize the connection
Verify client contacts are still set up
Meeting processed but no requirements generated
Possible causes:
The meeting didn't contain actionable content
Audio quality was too poor for transcription
The recording was too short (under 1 minute)
Solution:
Check the Files tab to see if the recording was uploaded
Review the recording to confirm it has clear audio
Try re-uploading manually if needed
Can't find the recording in my project
Check:
Files tab in the project
Wait for processing to complete (can take a few hours)
Verify the recording was actually captured (check Google Drive)
Make sure you're looking in the correct project
Best Practices
Client Contact Management
Keep emails current:
Update client contact emails when people change
Add new stakeholders as soon as they join the project
Remove contacts who are no longer involved
Use specific emails:
Add individual stakeholder emails, not group/distribution lists
Use the exact email they'll join meetings with
Verify emails before important discovery sessions
Recording Strategy
Record selectively:
Not every meeting needs to be recorded
Focus on discovery sessions, requirements reviews, and stakeholder decisions
Internal team meetings may not need processing
Use descriptive meeting titles:
Helps when recordings go to the manual assignment queue
Makes it easier to find recordings later
Example: "Acme Corp - CRM Discovery Session 3" vs. "Meeting"
Inform participants:
Let attendees know the meeting will be recorded
Explain that recordings are used for requirements documentation
Some participants may need to consent depending on local laws
Quality Control
Test the integration:
Record a short test meeting with a client contact
Verify it processes correctly
Check that requirements are generated as expected
Review generated requirements:
Don't assume all auto-generated requirements are perfect
Review and refine requirements after each meeting
Use AI Review to identify unclear requirements
Check citations:
Verify that requirements link back to the correct meeting timestamps
Use citations to validate requirement accuracy