Connecting your Google Calendar

Connecting a calendar is what turns your booking page from a schedule on paper into one that knows when you are actually busy. It is a separate step from signing in, and it is the single most common reason a new booking page shows no times.

How to connect

1. Open Settings in the app.
2. Under calendar connections, start the Google connection and choose the Google account whose calendar you want checked. It does not have to be the account you signed in with.
3. Approve the two calendar permissions Google shows you (described below). The first calendar you connect becomes your target calendar — the one new booking events are written to.

You can connect more than one calendar. Each connection has two independent switches: whether it is checked for conflicts, and whether it is the target for new events. A common setup is a work calendar as the target with a personal calendar conflict-checked but never written to.

What we ask for, and what it means

Free/busy

The start and end times of your busy blocks. So a booking link can't offer a slot you're already committed to. We request the granular free/busy scope, which cannot return event titles, guests, descriptions, or attachments — that limit is enforced by Google, not just promised by us.

Events on calendars you own

The list of calendars in your account — their names, not their contents. So you can tick which calendars should be checked for conflicts, instead of copying a Calendar ID out of Google's settings and pasting it to us. It returns the list and nothing else: this scope cannot read a single event, and your busy times still come from the free/busy scope above, which Google keeps incapable of returning titles or guests. It is read-only — we cannot add or remove calendars from your list. What it does mean, plainly: we see what your calendars are called.

Events on calendars you own

Permission to create and manage events on calendars you own. So a confirmed booking becomes a real calendar invite with a Google Meet link. Google publishes no Calendar scope restricted to the events an app created, so this is the narrowest write scope that lets us book at all — unlike the free/busy line above, this is a limit we keep, not one the API enforces. Our code only ever creates and manages the events Neos Meet books, and never lists or reads your other events. It does not cover calendars merely shared with you.

Sign-in is a third, separate grant covering your name, email address, and profile photo. It carries no calendar access at all, which is why you can use Neos Meet without ever connecting a calendar — you just will not get conflict checking.

What happens if you don't connect one

This is deliberate: the alternative is a booking page that cheerfully sells a slot you are already sitting in a meeting for. The same rule applies per host on a team link — a teammate who has not connected a calendar contributes no times to the pool.

Other consequences of running without a calendar:

• No calendar event and no Google Meet link is created for confirmed bookings.
• You still receive the host notification email for every booking, so you are never left unaware that someone booked you.
• Bookings made through Neos Meet still block each other — that check is in our own database.

If a connected calendar stops working

If you revoke access from your Google account, change your Google password in a way that invalidates the grant, or delete the connected calendar, the free/busy query starts failing. Neos Meet fails safe in exactly the same direction: the affected host is treated as unavailable for the whole window rather than assumed free. So a sudden empty booking page on an account that used to work usually means a broken grant — reconnect from Settings.

Revoking access

Disconnect a calendar from Settings at any time, and independently revoke the grant from your Google Account permissions page. Revoking stops all future reads and writes immediately.

Which calendars are supported

Google Calendar only, today. Outlook and Microsoft 365 are on our roadmap — they are not available yet, and we would rather tell you that here than have you find out mid-setup.

Still stuck?

Email support@neos.network with your booking link and, if there is one, the exact time an invitee tried to book. A real person reads it — there is no bot in front of us.