Files & knowledge · wired today
Google Calendar, wired into your agent workforce
Documents and wikis are the long-term memory agents reason over. The Google Calendar connector is one of 205 executable connectors and gives agents 3 read-only tools, with the credential held in the vault and every call receipted.
Connecting Google Calendar takes one credential
You provide service account json from your Google Calendar account; Quox sends it as a Google service account. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Google Calendar's own API documentation ↗ covers creating and scoping the credential.
What agents can run against Google Calendar
list_calendarsList the calendars on the service account's calendar list, with their IDs and access roles
list_eventsList events on one calendar, optionally bounded by a start and end time. Recurring events are expanded into single instances
get_eventGet one calendar event by ID
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
How proven is this?
This connector was blind shape-proven against the real Google Calendar API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Google Calendar integration FAQ
What can Quox agents do with Google Calendar?
Agents can run 3 read-only tools against Google Calendar: list calendars, list events, get event. Every call is receipted in the evidence trail.
What does the Google Calendar integration need?
You provide service account json from your Google Calendar account; Quox sends it as a Google service account. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Google Calendar credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Google Calendar connector?
This connector was blind shape-proven against the real Google Calendar API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.