Google Drive storage
Browse and manage Google Drive files, and import document snapshots into Apps.
Browse and manage Google Drive files, and import document snapshots into Apps.
What this connection offers
This is Google Drive storage, distinct from the tools entry. Browse folders, transfer files, and import app snapshots. Native Google documents export to PDF or XLSX when transferred; exported native originals can remain at the source on a cross-provider move.
| Detail | Value |
|---|---|
| Available uses | folder and file operations |
| Sign-in | Service sign-in and consent |
| Catalogue identifier | google_drive |
| Connection scope | user |
| Direction | both |
Connect
- Open Connections, choose to connect a service, and select Google Drive with the uses listed above.
- Give the connection a recognisable name.
- Complete the service’s sign-in and consent window with the account you intend to use.
- Check the connection status and run a connection test where offered.
- Select this saved connection in the app, workflow step, storage browser, or Assistant task that needs it.
Connection settings
This connector declares no ordinary configuration fields. Its sign-in or managed provisioning flow supplies the access it needs.
Data operations
The offered data operations are list, read, write, delete, copy. Your role, provider access, and app policy can further restrict an operation.
Consent and account access
The Google Drive storage connection requests access to read and manage existing files available to the connected account, including writes and deletion, rather than only files created by this app. Consent also enables offline access so authorised background work can continue without an open sign-in window. Check the account and consent screen before connecting. Revoke the connection when this access is no longer needed.
Reconnect
If access expires or consent is revoked, open this connection and use its reconnect flow. Finish consent, test access, then rerun the dependent task. Keep the existing connection when possible so workflow references remain valid.
Diagnose a failure
Check the connected account, its permission to the target, the selected folder, table or collection, and the connection’s current status. A successful sign-in is not proof that a particular resource is shared with that account. An empty search or folder page is not necessarily an authentication error. Revoke access when it is no longer needed; deleting the connection can also affect its tools and synced data. See connection lifecycle.