Google Calendar: what this connector can do

Member·4 minutes to read

What this page is for

The setup guide is for whoever runs your organisation's Botseon deployment: how to register Botseon with the provider so its sign-in screen works. This page is the other half: what Google Calendar actually lets a bot do once it is connected to your account, what it asks you for along the way, its limits, and how to take the connection away again, in Botseon and at Google.

Search events, find free time, and schedule meetings.

What a bot can do with it

Read — Google Calendar tells a bot things, nothing changes

Tool	What it does
`google-calendar.list_events`	List events in a time range.
`google-calendar.get_event`	Read one event by id.
`google-calendar.find_free_time`	Find free slots across calendars.

Write — Google Calendar lets a bot change things

Tool	What it does
`google-calendar.create_event`	Create an event and invite its attendees.
`google-calendar.update_event`	Change an event and notify its attendees.
`google-calendar.cancel_event`	Cancel an event and tell its attendees.
`google-calendar.respond_to_event`	Accept, decline or tentatively accept an invitation, with an optional note to the organiser. eventTitle must be the event’s exact title.

The permissions it asks for, in plain words

Every call a bot makes through this connector is tagged with what kind of thing it is. Only the tags below ever apply here — a tag this connector's tools never carry is not listed, because it can never ask you for it.

read — Looks something up. Nothing changes, and nothing is sent anywhere. A bot never has to ask first for this.
write — Changes something inside the connected account — creates, edits or files something. Asks you first, unless you have told Botseon to always allow that exact action.
external_send — Sends something to someone outside Botseon — a message, a reply, an email, a post. Asks you first, unless always-allowed.
delete — Deletes something you would consider yours. Always asks first — there is no always-allow rule that ever covers this.

Limits

Search events, find free time, and schedule meetings. Nothing outside that list is possible through this connector, however a bot is asked to use it.

Google Calendar is also only ever as wide as the scopes your organisation's connected app actually requests — the exact scopes are on the setup guide, because narrowing or widening them is a decision for whoever runs your deployment, not for this page.

Disconnecting

In Botseon

Open Plugins from the sidebar, press this connector's card to open its detail page, and under Accounts press Remove next to the account — or Uninstall to remove the plugin and every account connected to it at once. Either one revokes the stored connection immediately: nothing more is read or changed through it from that moment on. Install a plugin walks through the same screen step by step.

At Google

Removing the account in Botseon also asks Google to revoke the token, when this deployment's connector is configured with a revoke URL. Confirm the grant is actually gone by opening Google's own account settings — the connected-apps, security or authorised-apps page covers it — and removing Botseon there too if it still shows up. That is also where you can revoke access without going through Botseon at all, which is worth knowing if you ever lose access to your Botseon account.

What Botseon keeps, and how your data is used

Whatever a bot reads or writes through this connector becomes part of your conversations and the record of that run — the same records, and the same retention schedule, as everything else a bot works on. Botseon is the processor for that content; your organisation decides what it may read and remember, and can delete it sooner than the schedule would on its own.

Your data is sent to a model provider only to produce the bot's answer, and for nothing else — it is not used to train any model. The Privacy Policy's Models and How long we keep it sections have the full detail, including exactly how long each kind of record is kept for.