Connecting Google Calendar to Pilotiko
A straight answer: what is written, what is verified and what is still missing.
Today, Pilotiko runs your bookings and open slots from its own scheduler, with no Google account needed. The Google Calendar connector can read your busy times and create events with invitations. Status: Being commissioned: the connector is written and tested against a test server; it has not yet been verified with a real account.
In short
- Pilotiko's own scheduler already works on its own: online booking, real open slots and suggested assignment.
- The Google connection asks for the calendar.events scope, plus openid and email to show which account is linked.
- A meeting that sends invitations always waits for a person's approval.
- The connector has not been used with a real Google account yet; that first real test is the next validation step.
What does the Google Calendar connection do?
Two jobs: knowing when you are already booked, and putting meetings planned in Pilotiko into your Google calendar, with a Google Meet link when one is needed.
Pilotiko already has a scheduler of its own. It works out open slots from your team's hours and the appointments it knows about. But plenty of people live in Google Calendar: a client lunch, a dental appointment, a training day. Linking the two keeps Pilotiko from offering a customer a time when the person is away, and saves you from entering the same meeting twice.
To do that, Pilotiko asks Google for three permissions. The main one, calendar.events, is described by Google as "View and edit events on all your calendars" [1]. The other two, openid and email, only identify which account is connected. This connection does not ask for Gmail or Drive; sending email goes through the Gmail connection, which is separate.
One technical point, stated plainly: to read busy times, the connector calls Google's freeBusy method. Google's reference lists the scopes that method accepts: calendar.readonly, calendar, calendar.events.freebusy or calendar.freebusy [2]. None of them is in the scope list Pilotiko requests today. Reading availability will therefore have to be adjusted and checked during the first test with a real account, before it is switched on.
- Read from Google: your list of calendars, and busy periods (start and end only) over a given range.
- Written to Google: an event with a title, description, time, attendees and, on request, a Google Meet conference; later changes or a cancellation.
- Invitations: Pilotiko asks Google to notify attendees (sendUpdates=all) when it creates, moves or cancels a meeting.
- Approval: scheduling a meeting that sends invitations requires a person's approval. The assistant suggests; you decide.
- Checks: every step (meeting, event, invitation) is read back; if one fails, what was already created is undone.
How do I connect Google Calendar to Pilotiko?
- 1
Open the Connections page
In Pilotiko, go to Connections and find the Google Calendar card. If Pilotiko has not switched this provider on for your account yet, the card says so instead of showing a button that leads nowhere.
- 2
Pick the Google account
Click Connect. You are sent to Google, where you choose the account that holds the business calendar or your own.
- 3
Read the consent screen
Google lists what is requested: see and edit events on your calendars, plus your address and identity. Nothing else.
- 4
Approve and come back
Once you agree, Google sends you back to Pilotiko with a one-time code. Pilotiko swaps it for tokens and encrypts them straight away.
- 5
Check the status
The card switches to Connected. If a token renewal fails, it switches to Reconnect needed, never to a silent failure.
What is available, being commissioned or coming soon?
| Feature | Status | Detail |
|---|---|---|
| Online booking and open slots from Pilotiko's scheduler | Available | Works without Google, from your team's hours. |
| "Add to my calendar" .ics file for the customer | Available | iCalendar format that Google, Apple and Outlook can open. |
| Reading busy times in Google Calendar | Being commissioned | Code written; the freeBusy scope must be added before the first real test. |
| Creating, moving and cancelling events with invitations | Being commissioned | Tested against a test server, not yet with a real account. |
| Google Meet link on a meeting | Being commissioned | Requested from Google when the event is created. |
| Google Meet transcripts | Coming soon | Nothing is built yet. |
| Each employee's personal calendar | Coming soon | The category exists; no personal Google connector has shipped. |
Statuses come from Pilotiko's capability registry, where Google Calendar is listed as an adapter tested only against a fake server.
What would a week of synced bookings look like?
How is your Google data protected?
The tokens Google hands over are encrypted at rest (AES-256-GCM) and never leave the server; your browser never sees them. The connection link carries a one-time "state" value tied to your business and to your user, which expires after 10 minutes. The authorization code is also protected with PKCE, the IETF standard designed to stop an intercepted code from being reused [4].
Pilotiko only reads what a feature needs: busy hours, not what your personal appointments are about. Quebec's private-sector privacy act, as amended by Law 25, requires telling people why information is collected and that they may withdraw consent (s. 8), and consent given for specific purposes (s. 14) [3]. Google's screen and Pilotiko's card are there for exactly that: saying what the access is for before you grant it. More on the Security page and in the privacy policy.
Removing access works on both sides. In Pilotiko, Disconnect erases the tokens and records the action in the audit log. In your Google Account, open the linked third-party apps page, pick Pilotiko and remove its access; after that, the app can no longer reach your account.
What are the limits today?
- No real Google account has been connected or tested with this connector yet; that first real test is the validation step.
- The scope freeBusy needs has to be added before busy times are actually read.
- Bookings made by your customers live in Pilotiko's scheduler first; copying them to Google automatically is not switched on yet.
- Google Meet transcripts are not built. For meeting summaries, see Zoom and Microsoft Teams, both also being commissioned.
- If your business runs on Microsoft 365, the Outlook / Microsoft 365 page covers the equivalent; every connection is listed in the integrations index.
Frequently asked questions
Do I need Google Calendar to take bookings with Pilotiko?
No. Online booking and open-slot calculation work with Pilotiko's scheduler alone. Google Calendar adds your other commitments to the picture, once the connector has been verified.
Can Pilotiko read what my personal events are about?
For availability, the connector only asks for busy periods: a start and an end, no title. The calendar.events scope technically allows more, which is why Google's consent screen spells it out before you agree.
Will my customers get a Google invitation?
When a meeting is created in your Google calendar, Pilotiko asks Google to notify attendees. That step waits for a person's approval and is not yet running with a real account.
Does Pilotiko add a Google Meet link?
Yes, when the meeting is a video call and Google Meet is the chosen tool, Pilotiko requests one as the event is created. Like the rest of the connector, this has not been verified with a real account yet.
How do I cut off Pilotiko's access to my calendar?
Click Disconnect on Pilotiko's Connections page and the tokens are erased. Also remove the access from the third-party apps section of your Google Account so the permission is cancelled at Google too.
What about Apple Calendar or an iCal link?
Pilotiko does not connect to iCloud or subscribe to an iCal feed. It only gives your customers an "Add to my calendar" .ics file after a booking, which Apple, Google and Outlook can all open.
Sources
- Google for Developers, Choose Google Calendar API scopes (accessed on October 15, 2026).
- Google for Developers, Freebusy: query (Google Calendar API) (accessed on October 15, 2026).
- LégisQuébec, Act respecting the protection of personal information in the private sector (CQLR, c. P-39.1) (accessed on October 15, 2026).
- RFC Editor (IETF), RFC 7636 : Proof Key for Code Exchange by OAuth Public Clients (accessed on October 15, 2026).
Read next
Pilotiko integrations
Google Calendar, Outlook, Zoom, Stripe, LinkedIn, Cloudflare, Twilio and more: what each Pilotiko connection does today, with its status read from the code.
Outlook and Microsoft 365 with Pilotiko: your busy times and your outgoing mail
How Pilotiko connects to Outlook and Microsoft 365: Graph permissions requested, busy-time reading, sendMail, per-employee consent, real status and revoking.
Zoom and Pilotiko: scheduled meetings, checked and cleanly cancelled
Create, update and cancel Zoom meetings from Pilotiko with a waiting room: scopes requested, transcripts, what's still missing and the real status today.