In Meetings, each host connects their Google Calendar. Personyze then offers visitors only the times the host is really free, and puts every booking on that calendar — with a Google Meet link when the meeting happens on Meet.
What a connected calendar does
| What happens | |
|---|---|
| Busy times | Times the host is busy stop being offered. Personyze reads only when the host is busy — not the titles, the guests or anything else in their events. New busy time starts blocking bookings within a few minutes. |
| The booking | Each booking becomes an event on the host’s calendar, named for the meeting type and the visitor, with the visitor invited as a guest when they gave a valid email address. |
| The meeting link | A meeting type whose Where is Google Meet gets its Meet link from Google, on the host’s event. A Zoom meeting’s link goes on the event too — see Zoom integration. |
| Changes | A booking that is moved moves on the calendar; one that is cancelled comes off it. |
Connecting a host’s calendar
Each host connects their own calendar, once. The host needs no Personyze login: whoever manages Meetings can start the connection and let the host sign in on that screen.
- Go to Meetings → Hosts.
- In the host’s row, under Calendar, click Connect Google.
- Sign in with the Google account the host keeps their day in, and allow Personyze. Signing in with a second, personal account is the most common mistake.
- You come back to Hosts, which says Calendar connected. The host’s Calendar cell reads connected, with the account’s address under it — check it is the right one.
One calendar per host. Microsoft 365 calendars can’t be connected; Hosts offers Connect Google.
Which link a booking gets
The meeting type decides where the meeting happens. Set it in Meetings → Meeting types, under Where:
| Where | What the booking gets |
|---|---|
| Google Meet | A Meet link, made by Google on the event — so the host needs their Google Calendar connected. |
| Zoom | A Zoom room, for the host or for the whole account — see Zoom integration. A calendar is still what blocks busy times: Zoom cannot tell Personyze when a host is busy. |
| Phone, In person, A link I provide | No generated link. A connected calendar still gets the event. |
| Microsoft Teams | No link: it is listed, but no host can connect Microsoft 365, which is where a Teams link would come from. For Teams, use A link I provide with a standing Teams meeting link. |
Webex, Whereby or any other standing room link needs no integration: choose A link I provide and paste the link. It goes into the confirmation, the reminders and the calendar invite.
What the Calendar cell says
| The cell reads | What it means | What to do |
|---|---|---|
| connected | Busy times are read and bookings are written. | Nothing. |
| needs attention | The calendar answered with an error, shown under the address. Busy times may be out of date. | Reconnect. |
| disconnected at Google | The access was withdrawn on Google’s side — the host removed Personyze from their Google account, or the access expired. | Disconnect, then connect again. |
Disconnecting a calendar
Click Disconnect in the host’s Calendar cell. Personyze stops reading the calendar, so hours it was blocking become bookable again straight away, and the permission is withdrawn from the Google account too. Meetings already booked keep their events.
Inside a Meetings campaign, connecting and disconnecting are saved at once — Calendar disconnected. Saved at once. — not with the campaign’s Save. Deleting a host removes their calendar connection with them.
Your own Google app
Hosts connect through Personyze’s own Google app. To have the consent screen name your company instead, or because your Google Workspace limits which apps staff may allow, use an app of your own: Meetings → Connections, Google Meet and Google Calendar, Change.
- In Google Cloud Console, pick a project and enable the Google Calendar API.
- Set up the OAuth consent screen (Internal is fine for a Workspace).
- Under Credentials, create an OAuth client ID of type Web application, and add the Authorised redirect URI the Connections screen shows.
- Enter its Client ID and Client Secret, and click Save.
The next host who connects goes through your app. A host who is already connected stays on the app they allowed; they move to yours only if they disconnect and connect again. Remove goes back to the built-in app.
The Google Calendar card
Integrations → Marketplace has a Google Calendar card, and the Book meetings goal lists it. A calendar is connected per host, so the card counts the hosts connected — only hosts who can be booked — and Open Hosts takes you to the buttons.
Troubleshooting
A host was double-booked.
Check their Calendar cell reads connected and shows the address they really use. New busy time takes a few minutes to start blocking.
A booking has no Meet link.
Under Meetings → Bookings it reads No joining link; point at it for the reason. Check the meeting type’s Where is Google Meet and the host’s Calendar cell reads connected.
The booking is not on the host’s calendar.
The host has no calendar connected, or the cell says needs attention. Reconnect it; bookings made from then on are written.
Related
- Book a meeting — hosts, availability, meeting types and the booker
- Zoom integration — a Zoom meeting for every booking
- A booking page of its own — the booker at its own address, and the booking email
- Integrations — every integration, and where it is connected