Google Workspace Connector
Sync Google Workspace directory and calendar activity into your warehouse for meeting, scheduling, and collaboration analytics.
Evaluating against Fivetran? See how Supaflow handles Google Workspace pricing, connector quality, and Snowflake deployment side-by-side.
Supaflow vs FivetranWhy Supaflow
All connectors included
Every connector is available on every plan. Pricing does not increase with connector count.
Pay for compute, not rows
Credit-based pricing. Usage scales with your pipelines, not with row counts.
One platform
Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.
Capabilities
Domain-Wide Read Access
Use Google Workspace domain-wide delegation to read directory users and permitted non-resource calendars across the domain with a read-only service account.
Analytics-Ready Event Occurrences
Analyze recurring meetings as individual occurrences with their actual start and end times, attendees, organizer, location, conference details, visibility, and cancellation status.
Shared Calendar Coverage
Choose primary calendars, primary plus selected calendars, or every non-resource readable calendar. Virtual calendars remain opt-in, and shared calendars are read once even when several users can access them.
Native Incremental Calendar Sync
After the initial read, calendar event series and occurrences use Google Calendar change tracking. Supaflow handles invalidated change tokens with a clean resync.
Controlled Rollout and Backfill
Limit the source to selected users or organizational units, include suspended users only when needed, and set separate historical and future event windows.
Supported Objects
Directory and calendar membership
Users
Full-refresh directory profiles, account status, and organizational-unit assignments.
User calendars
Full-refresh calendar memberships and access context for included Workspace users.
Calendar activity
Calendar event series
Incremental recurring-event definitions and schedules.
Calendar event occurrences
Incremental one-off events and expanded recurring instances for meeting-level analysis.
Not yet supported
Room and resource inventory
Room and resource calendars, their events, and Workspace resource inventory are not synced today.
Calendar ACLs, calendar settings, and write operations
The connector is read-only and does not expose access-control or user-settings objects.
How It Works
Prepare Google Cloud
Create or select a Google Cloud project, enable the Admin SDK API and Google Calendar API, and create a service account and JSON key.
Authorize domain-wide delegation
In the Google Admin console, authorize the service account OAuth client ID for read-only directory users, calendar events, and calendar-list access. Calendar-list access is required for selected or all-readable calendar modes.
Enter the delegated administrator
Upload the service-account JSON key and enter the Workspace administrator email the connector will impersonate. Keep Workspace Customer ID as my_customer unless you intentionally use a specific customer ID.
Choose sync scope
Select the calendar scope and optionally restrict users by email or organizational unit. Set the historical and future event windows for your analytics needs.
Test and save
Click Test & Save. Supaflow verifies delegated authentication, directory discovery, and the calendar permissions required by the selected scope mode.
Use Cases
Meeting load and focus-time analysis
Measure scheduled meeting hours by user, team, day, and week to understand how much time remains for focused work.
Collaboration pattern reporting
Analyze organizer and attendee patterns across teams, recurring meetings, and shared calendars while respecting the event details users are permitted to see.
Calendar operations and adoption
Track active calendars, event volume, cancellations, recurring-meeting behavior, and conferencing usage alongside directory and organizational-unit context.
Frequently Asked Questions
Can the connector sync calendars for every Workspace user?
Yes. With domain-wide delegation and no user or organizational-unit filters, the connector discovers all directory users. Suspended users remain in the Users object, while their calendars are excluded by default unless Sync Suspended User Calendars is enabled.
Does it include shared calendars?
Yes. Primary and Selected includes selected shared calendars, and All Readable includes every non-virtual, non-resource calendar visible to included users. At least one included user must have read access.
How are recurring events represented?
Recurring definitions are available in Calendar Event Series, while Calendar Event Occurrences contains one row per expanded instance. This makes individual meetings directly usable for duration, attendance, cancellation, and scheduling analysis.
Does the initial history window delete older warehouse data later?
No. Initial Calendar History controls the backfill boundary when a calendar is first added. It is not rolling retention, so previously loaded history is not aged out. The future window advances for both one-off events and recurring occurrences on later syncs.
Which Google OAuth scopes are required?
Authorize admin.directory.user.readonly and calendar.events.readonly for Primary Only. Also authorize calendar.calendarlist.readonly for Primary and Selected or All Readable.
How does Supaflow handle Google Calendar API quotas?
Google applies Calendar API quotas per project and per user. Supaflow retries transient rate limiting automatically with backoff. Large domains or broad calendar scope can take longer to sync and may benefit from narrower user filters or off-peak scheduling.
Does the connector sync calendar rooms and resources?
No. Room and resource calendars, their events, and Workspace resource inventory are excluded today. Events on supported user and shared calendars can still contain location or attendee details that reference a resource.
Can I run Google Workspace pipelines natively inside Snowflake?
Yes. Supaflow runs as a Snowflake Native App through Snowpark Container Services, so extraction and loading can run inside your Snowflake account.
Need a connector we don't support yet?
Build one with AI-powered Connector Dev Skills.
Learn More About the Connector SDK
