Integrations/Google Calendar

Control what your AI agents do in Google Calendar.

Let your team build AI agents for Google Calendar. Bollard AI controls what each one can do, calendar by calendar.

Request early accessSee how it works →
Google Calendar
Scheduling Agent
Team calendar CalendarOffReadFull use
Exec calendar CalendarOffReadFull use
Personal calendar CalendarOffReadFull use
Change calendar sharing
What agents can do

Set what each agent can do in every calendar.

Each calendar gets one of three levels: Off, Read, or Full use. Anything not allowed is denied.

Off
No access
The agent can't see the calendar or that it exists.
Read
Read-only
The agent can read events and free or busy times on that calendar. It can't change anything.
Full use
Create and update
The agent can create, move, and update events on that calendar.

Some actions stay off until explicitly turned on

Each one exposes a calendar to others or removes events for good, so it could override the limits set on individual calendars.

Changing who a calendar is shared withDeleting events or whole calendarsTransferring ownership of a calendar
Set up & manage

Connect once. Manage everyone from there.

Connect once, then control access person by person. No new keys to hand out.

Step 1 · Set up

Connect once, company-wide

An admin connects your company's Google Calendar a single time and chooses which calendars it covers. Any calendar left out stays out of reach for every agent.

Step 2 · Manage

Control access per person and agent

From one dashboard, set what every person and their agents can reach. Change it any time, with no new keys for anyone.

OffNo access
ReadRead-only
Full useRead, create, move, and update events on a single calendar
Example

A team scheduling agent.

A scheduling agent books events on the team calendar and can read the exec calendar, but it can't open personal calendars or change sharing.

Team calendar CalendarOffReadFull use
Exec calendar CalendarOffReadFull use
Personal calendar CalendarOffReadFull use

Manage access

ALLOWEDScheduling Agent created an event on the Team calendar
ALLOWEDScheduling Agent read the Exec calendar
BLOCKEDScheduling Agent tried to open a Personal calendar, denied by default

Monitor activity

The security model

Top-tier security.

Bollard AI is access control for AI agents. It sits between your agents and Google Calendar, so they never hold your Google Calendar keys and never reach Google Calendar directly.

Everything runs through Bollard AI

Agents send their requests to Bollard AI, not to Google Calendar. Bollard AI checks each one against your rules and passes only the allowed requests through.

Denied by default

Every calendar starts off-limits, and changing how a calendar is shared is held back on top of that. An agent gets in only where you've allowed it, and anything Bollard AI doesn't recognise is refused and held for review, never waved through on a guess.

Your keys stay sealed

Your Google Calendar keys are sealed in a vault unique to your company and never shown again. Bollard AI unlocks them only for the instant an allowed request needs it.

Activity you can read

Every attempt is recorded in plain English: who or which agent, what they tried, which calendar or event, and the decision. The record is readable and can't be edited after the fact.

Questions

Google Calendar, answered.

Does connecting Google Calendar hand Bollard AI every calendar?+
Only what's connected. An admin chooses which calendars Bollard AI covers, and that sets the most any agent could reach. Bollard AI doesn't browse or copy your calendars. It sits in front of them and checks every request the agents make, passing or blocking each one.
Can an agent share a calendar with outsiders?+
Not unless you turn it on. Changing who a calendar is shared with is held off by default, so an agent can book and read events without ever exposing a calendar to someone new, until you explicitly allow it.
Can an agent see more than the person who owns it?+
No. An agent reaches only what its owner reaches. An explicit Off always overrides an inherited permission.
Where do our Google Calendar keys live?+
Sealed in an encrypted vault, behind a key unique to your company. It's never shown again once connected, and Bollard AI unseals it only for the instant an allowed request needs it.
What happens when an agent tries something it's not allowed to do?+
Bollard AI blocks the request before it reaches Google Calendar, and the blocked attempt lands in the activity record with the reason.
How do we connect Google Calendar?+
An admin connects the company's Google Calendar once. Bollard AI seals the connection and builds the list of calendars to set rules for. From then on, all management happens in the Bollard AI dashboard.
Early access

Put your team's agents to work in Google Calendar, without the risk.

We're onboarding our first development partners now. Tell us about your setup and we'll be in touch.

Request early accessAll integrations →