Google Calendar

Connect your Google Calendar data to Airweave

Overview

The Google Calendar connector allows you to sync data from Google Calendar into Airweave, making it available for search and retrieval by your agents.

Configuration

GoogleCalendarSource

Google Calendar source implementation (read-only).

Retrieves and yields Google Calendar objects (CalendarList entries, Calendars, Events, and Free/Busy data) as entity schemas defined in entities/google_calendar.py.

View Source Code

Explore the Google Calendar connector implementation

Authentication

This connector uses OAuth 2.0 with refresh token.

You can connect through the Airweave UI, which will guide you through the OAuth flow.

Entities

The following data models are available for this connector:

GoogleCalendarCalendarEntity

Schema for a Google Calendar object (the underlying calendar resource).

See: https://developers.google.com/calendar/api/v3/reference/calendars

Field	Type	Description
calendar_id	str	Unique identifier for the calendar.
summary	Optional[str]	Title of the calendar.
description	Optional[str]	Description of the calendar.
location	Optional[str]	Geographic location of the calendar.
time_zone	Optional[str]	The time zone of the calendar.

GoogleCalendarListEntity

Schema for a CalendarList entry, i.e., how the user sees a calendar.

See: https://developers.google.com/calendar/api/v3/reference/calendarList

Field	Type	Description
calendar_id	str	Unique identifier for the calendar.
summary	Optional[str]	Title of the calendar.
summary_override	Optional[str]	User-defined name for the calendar, if set.
color_id	Optional[str]	Color ID reference for the calendar.
background_color	Optional[str]	Background color in HEX.
foreground_color	Optional[str]	Foreground color in HEX.
hidden	bool	Whether the calendar is hidden from the UI.
selected	bool	Indicates if the calendar is selected in the UI.
access_role	Optional[str]	The effective access role that the authenticated user has on the calendar. E.g., ‘owner’, ‘reader’, ‘writer’.
primary	bool	Flag to indicate if this is the primary calendar.
deleted	bool	Flag to indicate if this calendar has been deleted.

GoogleCalendarEventEntity

Schema for a Google Calendar Event.

See: https://developers.google.com/calendar/api/v3/reference/events

Field	Type	Description
event_id	str	Unique identifier for the event.
status	Optional[str]	Status of the event (e.g., ‘confirmed’).
html_link	Optional[str]	An absolute link to the event in the Google Calendar UI.
created_at	Optional[datetime]	When the event was created.
updated_at	Optional[datetime]	When the event was last modified.
summary	Optional[str]	Title of the event.
description	Optional[str]	Description of the event.
location	Optional[str]	Geographic location of the event.
color_id	Optional[str]	Color ID for this event.
start_datetime	Optional[datetime]	Start datetime if the event has a specific datetime. (DateTime from ‘start’ if ‘dateTime’ is present.)
start_date	Optional[str]	Start date if the event is an all-day event. (Date from ‘start’ if ‘date’ is present.)
end_datetime	Optional[datetime]	End datetime if the event has a specific datetime. (DateTime from ‘end’ if ‘dateTime’ is present.)
end_date	Optional[str]	End date if the event is an all-day event. (Date from ‘end’ if ‘date’ is present.)
recurrence	Optional[List[str]]	List of RRULE, EXRULE, RDATE, EXDATE lines for recurring events.
recurring_event_id	Optional[str]	For recurring events, identifies the event ID of the recurring series.
organizer	Optional[Dict[str, Any]]	The organizer of the event. Usually contains ‘email’ and ‘displayName’.
creator	Optional[Dict[str, Any]]	The creator of the event. Usually contains ‘email’ and ‘displayName’.
attendees	Optional[List[Dict[str, Any]]]	The attendees of the event (each dict typically has ‘email’, ‘responseStatus’, etc.).
transparency	Optional[str]	Specifies whether the event blocks time on the calendar (‘opaque’) or not (‘transparent’).
visibility	Optional[str]	Visibility of the event (e.g., ‘default’, ‘public’).
conference_data	Optional[Dict[str, Any]]	Conference data associated with the event, e.g., hangout or meet link.
event_type	Optional[str]	Event type. E.g., ‘default’ or ‘focus’.

GoogleCalendarFreeBusyEntity

Schema for a FreeBusy response entity for a given calendar.

See: https://developers.google.com/calendar/api/v3/reference/freebusy

Field	Type	Description
calendar_id	str	ID of the calendar for which free/busy is returned.
busy	List[Dict[str, str]]	List of time ranges during which this calendar is busy.

Integrate Airweave with Google APIs on localhost

This guide will walk you through connecting Google Workspace APIs to Airweave when running locally. Google provides extensive documentation on setting up your workspace. Below is a streamlined process for connecting Google APIs to Airweave.

Create a Google Cloud project for your Google Workspace (if you don’t already have one)
Enable the Google Workspace APIs for Gmail, Google Calendar, and Google Drive
Configure Google OAuth 2.0 consent screen
Under Audience, select Make external and add test users
Under Data Access, add the following scopes:

https://www.googleapis.com/auth/docs
https://www.googleapis.com/auth/drive.photos.readonly
https://www.googleapis.com/auth/drive
https://www.googleapis.com/auth/drive.readonly
https://www.googleapis.com/auth/drive.metadata
https://www.googleapis.com/auth/drive.metadata.readonly
https://www.googleapis.com/auth/gmail.readonly
https://www.googleapis.com/auth/calendar.events.public.readonly
https://www.googleapis.com/auth/calendar.freebusy
https://www.googleapis.com/auth/calendar.readonly
https://www.googleapis.com/auth/calendar.calendars.readonly
https://www.googleapis.com/auth/calendar.events.owned.readonly
https://www.googleapis.com/auth/calendar.events.readonly

Create OAuth client ID credentials

Under “Authorized redirect URIs,” click ”+ Add URI” and add the following URIs:

http://localhost:8080/auth/callback/gmail

http://localhost:8080/auth/callback/google_calendar

http://localhost:8080/auth/callback/google_drive

Locate the client ID and client secret from your newly created OAuth client. Add these credentials to the dev.integrations.yml file to enable Google API integration.