This page describes how to create a data store for Google data sources, such as Cloud Storage or Google Drive.
To import data from a third-party data source, see Connect a third-party data source .
Generally Available
- Import from BigQuery
- Import from Cloud Storage
- Sync from Google Drive
- Sync from Gmail
- Sync from Google Calendar
- Sync people data
- Import from Cloud SQL
- Import from Spanner
- Import from Firestore
- Import from Bigtable
- Import from AlloyDB for PostgreSQL
- Create a data store using Terraform
Public Preview
- Sync from Google Chat (Preview)
- Sync from Google Groups (Preview)
- Import people data from a custom source (Preview)
- Enable NotebookLM Enterprise as a search source (Preview)
- Connect to data from AlloyDB for PostgreSQL (Preview)
Supported actions
Expand the data store name in the following list to reveal the available actions for each.
Google Calendar
Launch date
Action
Description
12/12/25
Create Calendar Event
Creates an event in your calendar.
Update Calendar Event
Updates the metadata for an event in your primary calendar.
Google Chat
Launch date
Action
Description
5/11/26
Create space
Creates a chat space in Google Chat.
Reply to thread
Replies to a chat thread in Google Chat.
Gmail
Launch date
Action
Description
3/23/26
Create label
Creates a new label in Gmail.
Add label to message
Add one or more existing labels to an email message or draft.
Send message
Sends an email message to the recipients.
Download attachment
Downloads an attachment from a Gmail message.
Send message with attachments
Sends an email message with attachments to the recipients.
Google Drive
Launch date
Action
Description
03/18/26
Create folder
Creates a new folder in Google Drive.
Copy file or folder
Copies a file or folder within Google Drive.
Download file
Downloads a file from Google Drive.
Upload file
Uploads a file to Google Drive.
Troubleshoot data ingestion
If you're using customer-managed encryption keys
and data import fails
(with error message The caller does not have permission
), then make sure
that the CryptoKey Encrypter/Decrypter IAM role
( roles/cloudkms.cryptoKeyEncrypterDecrypter
) on the key has been granted to
the Cloud Storage service agent. For more information, see Before you begin
in "Customer-managed encryption
keys".
