By the end of this guide, every confirmed booking will automatically create a Google Meet room and include the video link in confirmation emails sent to both you and the attendee. No manual room setup is required at any point.
Prerequisites
A Google OAuth app configured with
GOOGLE_CLIENT_ID
and
GOOGLE_CLIENT_SECRET
— see the
Google OAuth App Setup
guide
Google Meet API
enabled in your Google Cloud project — Meet rooms are created through the Google Meet API.
In Google Cloud Console
→ APIs & Services
→ Library, search for "Google Meet API" and click Enable.
Enabling the OAuth scope alone is not enough; until the API is switched on, room creation fails with a
SERVICE_DISABLED
error
Google Meet
connected in Tymeslot — go to Settings
→ Integrations
and connect the Google account that should host your Meet rooms. This is independent of your
calendar: Meet works alongside any calendar provider (Google, Outlook, or CalDAV)
Which Google account creates the room?
Meet rooms are created on whichever Google account you connected as the Google Meet integration in Tymeslot. Both personal Gmail accounts and Google Workspace accounts support Google Meet at no extra cost — no paid plan is required for basic Meet.
How It Works
When a booking is confirmed, Tymeslot calls the Google Meet API to create a standalone
meeting space
and includes the resulting link in the booking confirmation email. A meeting space is
not
a calendar event, so Google Meet never writes a second event into your calendar alongside
the booking — the booking itself is recorded once, on whichever calendar provider you use.
When the booking is cancelled, Tymeslot ends the meeting's active conference.
1
Enable Google Meet on a Meeting Type
Google Meet is enabled per meeting type through the location setting. Repeat for each meeting type where you want automatic Meet rooms:
Navigate to Dashboard → Meeting Types
Click Edit on the meeting type you want to update
Go to the Location tab
Select Google Meet from the location options
Click Save
Expected result: the meeting type card in your dashboard now shows "Google Meet" as the location.
From this point on, every new booking for this meeting type will have a Meet room created automatically
when the booking is confirmed.
Google Meet not listed as a location option?
If Google Meet
does not appear in the location list, your Google Meet integration is not connected. Go to
Dashboard
→ Integrations
→ Video, find the Google Meet row, and click Connect. Return here once it shows a connected status.
2
Confirm the Meet Link Appears After Booking
After a booking is confirmed for a Google Meet meeting type:
Navigate to Dashboard → Meetings
Click the meeting to open its detail view
The Meet URL (e.g., meet.google.com/xxx-xxxx-xxx) is shown under
Location
If the Meet link shows as "pending" or is absent, see the troubleshooting section below.
Attendee Experience
The booking confirmation email sent to attendees contains:
A clickable Google Meet link — clicking it opens the Meet room directly in the browser, no app required
The same Meet link is embedded in the ICS calendar invite — accepting the invite adds it directly to the attendee's calendar event
No Google account required for attendees
Attendees can join a Google Meet room as a guest without a Google account. They simply open the link in their browser and request to be admitted.
Troubleshooting
Meet link is missing or shows as "pending" in the confirmation email
The most common cause is the Google Meet API
not being enabled in your Google Cloud project — navigate to
Google Cloud Console
→ APIs & Services
→ Enabled APIs
and check for "Google Meet API" in the list. If it is missing, enable it from the
Library
and retry. Also verify that your Google Workspace or Gmail account supports Meet (all standard accounts do).
Room creation fails consistently
Failed room creation is retried automatically via background jobs. If rooms consistently fail, check
Dashboard
→ Settings
→ Integrations
for integration health warnings
on the Google Meet row. A warning here usually means the OAuth token has expired or been revoked —
disconnect and reconnect the integration to refresh it.
Meet room created on the wrong Google account
Meet rooms are created on the Google account that connected the Google Meet integration. If you have
multiple Google accounts and the wrong one is connected, go to Settings
→ Integrations,
disconnect the current Google Meet connection, and reconnect using the correct account.
❓
Frequently Asked Questions
Google Meet links aren't being created — why?
Two conditions must both be true for Meet links to be generated. First, the
Google Meet API
must be enabled in your Google Cloud project — go to Google Cloud Console
→ APIs & Services
→ Enabled APIs
and confirm "Google Meet API" is listed. Second, Google Meet must be connected in
Tymeslot — go to Settings
→ Integrations
and verify the Google
Meet row shows a connected status. Both must be satisfied before Meet links will appear.
The Meet link in the confirmation email shows a placeholder — what's wrong?
A placeholder usually means the Google Meet API call failed at the time of booking. Tymeslot
retries failed room creations automatically via background jobs, so the link may appear shortly
after. If the placeholder persists, check the application logs for API errors — look for entries
referencing
google_meet
or a
SERVICE_DISABLED
response. A revoked or expired OAuth token is another common cause; disconnecting and reconnecting the
Google Meet integration in Settings
→ Integrations
will
refresh it.
Do I need a Google Workspace account for Google Meet?
No. Personal Google (Gmail) accounts fully support Google Meet at no cost. Workspace accounts
add organisational controls — such as restricting who can start or join meetings and enforcing
recording policies — but those are admin-level settings that do not affect the basic Meet link
creation Tymeslot performs.
Can attendees join without a Google account?
Yes. Google Meet allows anyone with the meeting link to join as a guest directly from their
browser — no Google account or app installation is required. The meeting host (the Google account
that created the room) must join for the call to begin unless the
Quick access
setting is enabled in Meet settings, which allows guests to enter without waiting for the host.
The Meet link works but I see 'waiting for host' — is that expected?
Yes, this is standard Google Meet behaviour. Guests who arrive before the host see a waiting
screen until the host joins. If you want attendees to be able to start the call without you,
enable Quick access
in your Google Meet settings (meet.google.com → Settings
→ Host controls). Note that Quick access is a per-host preference and is not configurable
from within Tymeslot.
Verification Checklist
Book a test appointment using a meeting type with Google Meet as the location, then confirm each of the following:
A Google Meet link appears under Location
in Dashboard
→ Meetings
→ meeting detail
The booking confirmation email contains the same Meet link
Opening the Meet link in a browser loads the Meet room and prompts for camera and microphone permissions
Auto-create Zoom meetings for every confirmed booking. Works with Zoom Pro, Business, and Enterprise accounts via OAuth — free Zoom accounts cannot create meetings programmatically.
Host video meetings with MiroTalk P2P — fully self-hosted, no subscriptions, peer-to-peer bandwidth. Covers Docker setup, reverse proxy, and TURN server config.
