Google Workspace connector reference

Important

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.

This page has reference information for the managed Google Workspace connector, including the supported source tables and their destination schema.

Supported source tables

The Google Workspace connector supports 33 source tables, one for each Google Workspace activity application, under the default source schema. Each table supports incremental ingestion. The connector uses the time field as the cursor field for incremental ingestion.

The supported tables are:

  • access_evaluation
  • access_transparency
  • admin
  • assignments
  • calendar
  • chat
  • chrome
  • classroom
  • cloud_search
  • contacts
  • context_aware_access
  • data_migration
  • data_studio
  • directory_sync
  • gcp
  • gemini_in_workspace_apps
  • graduation
  • groups
  • groups_enterprise
  • keep
  • ldap
  • login
  • meet
  • meet_hardware
  • mobile
  • profile
  • rules
  • saml
  • takeout
  • tasks
  • token
  • user_accounts
  • vault

Each table contains activity records from the Google Workspace Admin SDK Reports API. All tables share the same schema and support incremental ingestion with time as the cursor field.

Source tables Primary key Description Sync mode Cursor field
All 33 applications above lw_id Google Workspace activity events from the Admin SDK Reports API for various applications. Incremental time

Note

The gmail and drive applications aren't included in the list above. Use the dedicated Gmail connector and Google Drive connector connectors to ingest those sources.

Note

The Databricks UI ingestion wizard exposes 30 of these tables in its source-table selector. To ingest login, groups, or groups_enterprise, use API-based pipeline authoring or Declarative Automation Bundles.

Connector options

The Google Workspace connector supports the following configuration options beyond the pipeline settings available for all managed connectors:

  • start_datetime (optional): The backfill start date in ISO 8601 format (e.g., 2024-01-01T00:00:00Z). When not configured, the connector defaults to 180 days before the first sync. See Google Workspace connector limitations.

Destination table schemas

All 33 application tables share the following schema, derived from the Google Workspace Admin SDK Reports API activity envelope:

Primary key: lw_id Cursor field: time

Field Data type
lw_id STRING
time TIMESTAMP
kind STRING
etag STRING
id STRUCT<time: STRING, uniqueQualifier: STRING, applicationName: STRING, customerId: STRING>
actor STRUCT<profileId: STRING, email: STRING, callerType: STRING, key: STRING, applicationInfo: STRUCT<oauthClientId: STRING, applicationName: STRING, impersonation: BOOLEAN>>
ownerDomain STRING
ipAddress STRING
isAgenticAction BOOLEAN
networkInfo STRUCT<ipAsn: ARRAY<INT>, regionCode: STRING, subdivisionCode: STRING>
events ARRAY<STRUCT<type: STRING, name: STRING, status: STRING, resourceIds: ARRAY<STRING>, parameters: ARRAY<STRUCT<name: STRING, value: STRING, intValue: STRING, boolValue: BOOLEAN, multiValue: ARRAY<STRING>, multiIntValue: ARRAY<STRING>, messageValue: VARIANT, multiMessageValue: VARIANT>>>>
userDeviceInfo VARIANT
resourceDetails VARIANT

Note

These tables do not support SCD type 2 because they have VARIANT columns.

Incremental ingestion

Each table is ingested incrementally, using the time field as the cursor. When no start_datetime is configured, the connector backfills the previous 180 days. The Google Workspace Admin SDK Reports API retains activity logs for up to 180 days, so the connector can't ingest events older than that window. Different applications report with different lag windows; the connector applies per-application lookback to absorb this lag. See Google Workspace connector limitations.

  • Last updated on