Integration · Google Drive
Connect Google Drive to meinGPT
Load current Google Drive files directly into a chat or synchronise selected folders and shared drives into a central knowledge source.
Google Drive can be used in meinGPT in two ways. The direct connector searches current files with the signed-in Google user's permissions and loads selected content into the current chat. A Google Drive source in Cloud Vault synchronises selected folders or shared drives into a centrally managed index for repeated search and shared assistants.
On the direct path, each person connects through Google OAuth and the assistant searches or loads files only for a concrete task. On the Cloud Vault path, an administrator defines a folder or shared-drive scope and starts synchronisation. The shared index uses its own meinGPT access model; personal Drive rights are not copied automatically.
Use current files in chat
Searches Google Drive in the user's context and loads a selected file only for the current task.
- Best for
- Ad-hoc questions, current files, and personal work
- Freshness
- Live through the Google Drive API
- Permissions
- Permissions of the signed-in Google user
Make document collections centrally searchable
Synchronises approved folders or shared drives into a central index for repeated search.
- Best for
- Larger collections, repeated search, and shared knowledge spaces
- Freshness
- Periodic according to the configured sync
- Permissions
- Access rules of the meinGPT knowledge space
Source, permissions, and data residency are documented separately for each connector.
Typical workflows
- Find current files for a task
- Search a shared knowledge collection
- Extract decisions and actions
Compare connection paths
The same system can be connected differently depending on the task. Freshness, permissions, and scope determine the right path.
Direct connector
Use current files in chat
Searches Google Drive in the user's context and loads a selected file only for the current task.
- Best for
- Ad-hoc questions, current files, and personal work
- Access
- Read-only and only on explicit request
- Freshness
- Live through the Google Drive API
- Permissions
- Permissions of the signed-in Google user
- Scope
- Optionally restricted to selected folders
- Limitation
- The direct connector does not create a persistent shared index and does not write back to Drive.
Setup
- 1.Enable Google Drive on the assistant
- 2.Connect the Google account and optionally restrict folders
Cloud Vault
Make document collections centrally searchable
Synchronises approved folders or shared drives into a central index for repeated search.
- Best for
- Larger collections, repeated search, and shared knowledge spaces
- Access
- Read-only synchronisation
- Freshness
- Periodic according to the configured sync
- Permissions
- Access rules of the meinGPT knowledge space
- Scope
- Selected folders or shared drives
- Limitation
- Personal Google Drive permissions are not automatically reproduced as document rights in the central index.
Setup
- 1.Create the Cloud Vault source as an administrator
- 2.Define scope, synchronisation, and meinGPT access
What the integration makes possible
01
Find current files for a task
Use the direct connector to locate and load selected current files under the connected user's permissions.
02
Search a shared knowledge collection
Synchronise approved folders or shared drives and answer repeated questions with source references.
03
Extract decisions and actions
Read selected documents and return decisions, actions, owners, risks, and source files in a reviewable structure.
Clarify before starting
- 01Ad-hoc access or a shared index has been chosen.
- 02Folders or shared drives in scope are documented.
- 03Owners for OAuth, sync, access, and deletion are assigned.
Review the prompt and result openly
Search the approved Google Drive documents for Project ACME. Summarise the latest decisions, open actions, risks, and source files with dates.
Result
A table lists decisions, actions, risks, source files, and dates. No Drive file was changed.
Does this connection fit your use case?
We clarify the source, permissions, and connection required for the concrete use case. If the existing integration fits, you can move straight to setup afterwards.
Security and operations
Choose the direct connector when personal Google permissions must remain authoritative. For Cloud Vault, define the folder or shared-drive scope and meinGPT groups before synchronisation.
Known limitations
- 01The direct connector is read-only and does not maintain a shared index.
- 02Cloud Vault does not automatically inherit personal Google Drive permissions.
- 03Search quality depends on document text, structure, and OCR.
Frequently asked questions
No. It searches and loads selected files on demand. Cloud Vault is the separate path for a persistent shared index.