Appearance
Google Drive integration
The Google Drive integration is the shortest route from the documents you already have to a company brain that can answer from them.
What the Google Drive integration pulls
| Capability | Behaviour |
|---|---|
| Browse | Walks a folder recursively and lists what is there |
| Metadata | File name, type, size, modification time and folder path |
| Native Google files | Docs and Slides are exported as plain text, Sheets as CSV, before indexing |
| Uploaded files | PDF, DOCX, TXT, MD and CSV are extracted. Other types are downloaded but not indexed for content |
| Indexing | Documents are chunked, embedded and stored with a reference back to the source file |
What the Google Drive integration can be used for
Google Drive can be used for building a company brain from what already exists, without anyone rewriting internal documentation into a new system.
Google Drive can be used for grounding a chat widget, so an assistant answers from your own policies, specifications and price lists.
Google Drive can be used for grounding the content pipeline, so generated articles use your terminology, your product names and your claims rather than invented ones.
Google Drive can be used for keeping knowledge current, because a re-index picks up the documents that changed.
Google Drive can be used with scoped access, pointing at one folder rather than at a whole Drive.
Google Drive can be used for answer traceability, since every answer carries a reference back to the document it came from.
Grounding narrows the gap. It does not close it
An assistant reading your own documents is far more likely to be right than one working from general knowledge, and far less likely to invent a product name or a price. It is still a language model. The source reference on every answer is there so a person can check it, and for anything that carries money or a commitment, somebody should.
Google Drive combined with other integrations
| Combination | What it gives you |
|---|---|
| Drive + chat widget | Support answers grounded in real internal documents |
| Drive + content pipeline | Articles written in your language, from your material |
| Drive + Odoo | Documents and business records answering the same question together |
| Drive + MCP | Your assistant of choice querying the company brain from your editor |
What you need to connect Google Drive
- Google OAuth authorisation from Studio
- The folder to index
Scope the folder deliberately
Point the integration at the folder you mean. A company brain built from an entire Drive will happily answer questions about the salary spreadsheet somebody left in the wrong place.
Frequently asked
Are shared drives supported? Folders the connected account can open are supported. Some shared drive configurations restrict API access, so verify with a browse before you rely on it.
Does it copy my documents? It indexes their content and stores embeddings and chunks in your organisation's knowledge store, in the EU. The originals stay in Drive.
Can I exclude files? Yes, by scoping the folder and by knowledge tags that control which content a given assistant is allowed to read.
Which file types are indexed? Google Docs, Sheets and Slides, plus uploaded PDF, DOCX, TXT, MD and CSV. Images, audio and video are not indexed for content.