Connecting your tools

Connecting Google Calendar to an AI agent

Booking a meeting rarely costs fewer than four emails. An agent connected to Google Calendar consults your calendars and your availability, looks for a genuinely free slot, creates the meeting, changes or deletes it, and invites the participants. It is one of the few gains whose effect shows in the first week — and one of the few where the permission limit deserves explaining in detail.

1. What the agent does in the calendar

The connector talks to Google's Calendar interface, the one that works with an ordinary Gmail account — not only with a business subscription. Seven operations are available, the most useful being the search for a free slot:

Consult. Read the list of your calendars and your real availability, taking into account what is already booked.
Find. Search for a slot that suits several people, which is precisely the work everyone puts off.
Create, change, delete. Book the meeting, move it if needed, cancel it.
Invite. Add the participants, who receive Google's usual invitation.

Concretely, this turns “find us a slot next week with this client” into a single action rather than an exchange.

2. Three permissions, and not one more

The connector requests exactly three permissions: reading the list of your calendars, reading your availability, and managing meetings. That number is not a cautious setting — it is a constraint, and it deserves to be understood.

Those three permissions are the ones declared to Google for nullbot's consent screen. Asking for a single one more, even broader and even useful, would bring back the “unverified app” warning for every user. Wider access would therefore be paid for with an alert screen at every sign-in, for everyone. We prefer the narrow scope.

Practical consequence: what falls outside that scope is not reachable, whatever the request. It is an accepted limit, not an oversight.

3. Connecting your account

You sign in with your Google account, Google's screen displays the three permissions, you accept. The connection then requires designating the account and the calendar concerned: an agent connected to the sales calendar does not see the personal one.

There is a technical prerequisite, and it is flagged at connection time: the Google Calendar interface must be enabled in the Google Cloud project that holds your instance's credentials. It is a one-off step, done once and for all.

4. What stays under control

Booking a meeting is a write, and an invitation that has gone out cannot be quietly taken back: the person invited has received it. The default setting takes that into account.

Approval before writing is on by default. Creating, moving or deleting a meeting requires human approval until you have explicitly relaxed it. Many users end up relaxing it on simple creation and keeping it on deletion — that is a reasonable trade-off.
The scope is named. Account and calendar are designated at connection.
Spending is capped before the call, as for every agent: envelope exhausted, the call does not happen.

5. What it changes over time

It is one of the few connectors whose effect is visible immediately, then grows.

Week 1. Meeting requests stop dragging: the proposed slot goes out the same day.
Month 3. The calendar fills without anyone arbitrating by hand, and genuinely free slots get used instead of being lost between two exchanges.
Year 2. Booking is no longer a subject. And the time regained is not the booking time — it is the waiting between two replies.

Here too, no figure is promised: the gain depends entirely on the volume of meetings your business handles.

6. Frequently asked questions

Does the agent see the content of my private meetings?

It sees what the calendar you designated contains. If your personal and professional calendars are separate, connect only the second: that is the point of a named scope. For slot searching, the agent needs to know a period is busy, not what it is busy with.

Can it cancel a meeting on its own?

Deletion is a destructive action: it requires human approval by default, and that is the setting we recommend keeping. A cancellation goes out to every participant and leaves an unpleasant trace that no correction repairs.

Do I need a Google business account?

No for the calendar use itself: the connector uses the Calendar interface, which works with an ordinary Gmail account. The interface must, however, be enabled in your instance's Google Cloud project — a one-off step, flagged at connection time.

What if I use Calendly rather than Google Calendar?

Calendly is also in the catalogue and covers booking on the visitor's side, including its insertion into a page of your site. The two complement each other rather than replace each other: Calendly receives the request, the calendar holds the truth of your availability.