Repository navigation
add google calendar and contacts, and group the permissions by product - #99
Merged
hkonsti merged 1 commit intoOct 15, 2026
Conversation
hkonsti
force-pushed
the
hkonsti/google-10-calendar-contacts
branch
from
October 15, 2026 00:09
e98f604 to
ca5d6b5
Compare
…nd start google with nothing on Calendar is a nested events collection: the calendars, and each one's events from now on, soonest first. Agents can create and edit events, answer invitations, and invite guests, which is an action of its own since Google emails them. Contacts can be listed, searched, added and edited. Neither is ever deleted. The permissions show Gmail, Calendar, Drive and Contacts as sections, with Enable all and Disable all.
hkonsti
force-pushed
the
hkonsti/google-10-calendar-contacts
branch
from
October 15, 2026 00:20
ca5d6b5 to
ca5932d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Google connections now cover Calendar and Contacts. A sign-in asks for three more scopes:
calendar.events,calendar.calendarlist.readonlyandcontacts. These are narrower than fullcalendar, which would also let an agent delete calendars and change their sharing.Calendar is a nested
eventscollection: the calendars at the top, and inside each its events from now on, soonest first. A search that begins with a day,2026-10-15 standup, lists from that day on. Its actions are Read events, Create and edit events, Answer invitations (Accept, Decline, Maybe) and Invite guests. Guests are a field with an action of their own (Field.action, checked inrunAgentTool): inviting guests, or changing an event that already has some, needs Invite guests beyond the write, because Google emails them. An event without guests tells no one.Contacts is a
contactscollection over the People API: most recently changed first, Google's prefix search, and Add and edit contacts. An edit sends only the fields that changed and keeps labels like work or home. Events and contacts are never deleted.The permissions page shows actions grouped by product (
Action.group: Gmail, Calendar, Drive, Contacts), each section saying how many are on, with Enable all / Disable all at the top. A new Google connection now starts with nothing on.effectiveActionsnow followsrequiresall the way down, so Invite guests counts only while Read events does. Record links on the agent side are URL-encoded, since some calendar ids contain#.Tested only against mocked Google answers so far, not a real account. Existing connections show the new actions as "Not allowed at sign-in" until they sign in again. A self-hosted Cloud project also needs the Calendar and People APIs enabled. Once the stack is rebased onto main, the privacy policy (#85) needs Calendar and Contacts added to its list of Google data.
Stack: on #92.
Open workspace in Conductor