Google Meet Integration
Auto-create Google Meet rooms for every confirmed booking via the Calendar API. Attendees receive the link by email and can join without a Google account.
Auto-create Microsoft Teams meetings for every booked appointment, on the Microsoft account you connect.
Updated 23 September 2026
By the end of this guide, every confirmed booking will automatically create a Microsoft Teams meeting room and include the Teams join link in confirmation emails sent to both you and the attendee.
OUTLOOK_CLIENT_ID
and
OUTLOOK_CLIENT_SECRET
— see the
Microsoft Azure App Setup
guide
Calendars.ReadWrite
and User.Read
, plus
offline_access
so the connection survives without you signing in again. Nothing else is requested
POST /me/onlineMeetings
endpoint. That endpoint is the one that needs
OnlineMeetings.ReadWrite
and, in most tenants, an administrator to consent to it. Tymeslot never calls it, so the permission
is neither requested nor required: adding it to your Azure app only grants access that goes unused.
When a booking is confirmed, Tymeslot creates a calendar event on the connected Microsoft account
(POST /me/events)
with
isOnlineMeeting
turned on. Microsoft attaches a Teams meeting to that event and returns its join URL, which Tymeslot
stores and includes in the booking confirmation email and in the meeting detail view. For a work or
school account, Tymeslot names
teamsForBusiness
as the meeting provider; for a personal Microsoft account it leaves the provider unset and takes
whatever Microsoft attaches.
The Teams meeting is that calendar event, so the meeting also appears in the connected account's own calendar. If Microsoft creates the event but attaches no Teams meeting, which is what happens when the account cannot host one, Tymeslot deletes the event again rather than leaving an empty placeholder behind. The booking itself is unaffected: it stays confirmed, and the confirmation email goes out without a join link.
Every permission Tymeslot requests can be granted by the person signing in, so in most tenants no administrator is involved: you approve them on Microsoft's consent screen in step 2. Consent becomes an administrator's job only where the organisation has turned off user consent for third-party apps, and you will know because sign-in stops on a "Need admin approval" screen.
If that happens, your IT administrator grants consent once, for everyone:
Calendars.ReadWrite
and User.Read
are listed as Delegated
permissions
Microsoft Teams is connected as a video integration of its own, separate from any Outlook Calendar connection:
Expected result: Microsoft Teams appears in your list of video integrations, showing your Microsoft account.
OUTLOOK_CLIENT_ID
and OUTLOOK_CLIENT_SECRET.
Microsoft Teams is enabled per meeting type. Repeat for each meeting type where you want automatic Teams meetings:
Expected result: new bookings that use this location have a Teams meeting created automatically on confirmation.
You can tick several providers on the same location, for example Microsoft Teams alongside Google Meet or Zoom. The person booking then chooses which one the room is created on. See Meeting Locations for everything a meeting type's locations can do.
The booking confirmation email sent to attendees contains:
Tymeslot keeps the join link Microsoft returns for the event and nothing else, so the email carries no dial-in number and no conference ID. Anyone who needs to dial in can open the meeting in Teams, which shows whatever dial-in details the hosting account has.
The booking is confirmed but there is no Teams link in the email
Microsoft created the calendar event without attaching a Teams meeting, so Tymeslot removed the event again and announced the booking without a link. This is an account problem rather than a permissions one: confirm the connected account has a Teams licence in the Microsoft 365 admin centre under Users → Active users → select the user → Licences and apps, and that your organisation has not blocked Teams meeting creation for it. Once that is sorted, new bookings get a link; bookings already confirmed without one stay as they are.
Sign-in stops on a "Need admin approval" screen
Your organisation requires an administrator to consent to third-party apps. Ask your IT
administrator to grant consent for
Calendars.ReadWrite
and
User.Read
as described in step 1, then connect again.
Sign-in succeeds but Microsoft Teams never appears as a video provider
The integration is not showing as connected. Disconnect the Microsoft Teams video integration, connect it again, and confirm it reports a connected status before you edit the meeting type. If the dashboard shows a "Reconnect required" badge, Microsoft has rejected the stored credentials and reconnecting is what clears it.
Tymeslot records a join link only if Microsoft attaches a Teams meeting to the calendar event it creates. Where it does not, the booking is still confirmed, just without a link. The usual cause is the connected account itself: check that it has a Teams licence in the Microsoft 365 admin centre under Users → Active users → select the user → Licences and apps.
A missing
OnlineMeetings.ReadWrite
grant is not the cause. Tymeslot neither requests that permission nor calls the endpoint that
needs it.
No. That permission covers Microsoft's online meetings endpoint, which Tymeslot does not use: it
creates Teams meetings as calendar events, so
Calendars.ReadWrite
is the permission that matters. Adding
OnlineMeetings.ReadWrite
changes nothing about how Tymeslot behaves, and in most tenants it drags an administrator into a
connection that would otherwise need nobody.
Yes, provided the account has both a mailbox and a Teams licence. Tymeslot creates the Teams meeting as an event on the account's calendar, so it needs the mailbox to hold the event and Teams to attach the meeting to it. Business Basic includes both.
Some Microsoft 365 plans include Exchange and OneDrive but omit Teams. On one of those, the event is created with no Teams meeting attached, Tymeslot removes it again, and the booking is confirmed without a join link. To check, go to the Microsoft 365 admin centre → Users → Active users → select your account → Licences and apps and confirm a Teams-enabled licence is assigned.
No. Teams allows guests to join without a Microsoft account. Attendees open the join link in any modern browser and enter the meeting lobby as a guest — no sign-in, no Teams subscription, and no app installation required (though the desktop app can be used if preferred).
Yes. Microsoft Teams is connected on the Video tab and Outlook Calendar on the Calendars tab, and each is its own connection, signed in separately and stored separately. You can use Teams as a meeting location without syncing your Outlook Calendar, and vice versa; neither depends on the other being active.
This typically means the meeting was created under a Microsoft account that is no longer active, or the connected account in Tymeslot has been disconnected and reconnected as a different Microsoft account. Teams meetings are tied to the specific account that created them — if that account changes, existing meeting links become invalid.
Confirm that the Microsoft account shown in Dashboard → Integrations → Video is the same account that will host the meetings. If you recently reconnected the integration with a different account, existing booking links will not work; only newly created bookings will generate valid links under the new account.
Auto-create Google Meet rooms for every confirmed booking via the Calendar API. Attendees receive the link by email and can join without a Google account.
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.