Answer questions from designated folders
The workflow searches your designated folders and shared drives and answers with a file reference.
Google Drive integration
About this source
Gen8
Source: Google Drive integration
Managed AI service for SMEs. We set up, connect and manage; you stay in control.
© 2026 Gen8 VOF · Dutch Chamber of Commerce 92978789 · Delft
Integration · route: native
Your designated folders, readable by a workflow
For many organizations, Google Drive is both archive and workplace. Gen8 has its own integration that goes beyond files: Docs, Sheets and Slides content is accessible too. In the standard setup it reads; writing is a deliberate extension.
- Permissions stay in force
- EU hosting
- Visible approval
At a glance
Route: native
Components: Google Drive, Google Docs, Google Sheets, Google Slides
Capabilities
What the integration can do
Files. Search and read within designated folders and shared drives — to answer with source references or use a file as input for the next step.
Google Docs. Read document content and, if configured, create or update text. A report compiled from data is the typical use.
Google Sheets. Read spreadsheet data and update rows or values, for example an overview needing weekly additions.
Google Slides. Read presentation content and create or edit slides.
What does not happen: reorganizing folders, moving or deleting files. Cleanup stays with people.
Inspiration
What you can automate with this
A few examples of work you can hand over through this integration. We work out what fits your organisation together during scoping.
Compile a report
A Google Docs report built from data. A change starts as a proposal someone sees.
Add to the weekly overview
New rows or values in an overview needing weekly updates. After a settling-in period this can run automatically with logging.
Permissions and data
What access is needed
An administrator connects and designates folders or shared drives. Opening an entire Drive for convenience is exactly what we avoid — defining scope is the setup.
The workflow gets only necessary permissions: knowledge sourcing needs read access to designated folders, nothing more. Writing adds a permission and must be an explicit decision. Drive's permissions remain authoritative: the integration must not bypass what someone is allowed to see. Gen8 processing takes place in the EU.
Control
Where approval is required
Reading as a source needs no approval per question. Control comes earlier: selecting folders and deciding who may use the workflow.
Writing follows the usual principle. A document or spreadsheet change starts as a visible proposal. If a change works for months without correction and is small and reversible, it can become automatic with logging — updating a weekly overview is a good example; rewriting a customer report is not.
Evidence
What we can demonstrate
Google Drive has its own Gen8 integration with separate tools for files, Docs, Sheets and Slides. Hence the native route. Microsoft equivalents are covered in SharePoint and Microsoft 365; making documents queryable is covered in documents and knowledge. For storage without its own integration, see MCP, API and custom development.
Update a recurring overview
Plan01Only designated folders and shared drives included
Action02Source files found and read
Action03Docs and Sheets content read
Action04Addition prepared with visible difference
Reflect05The file is shared: change proposed, not applied
Proposal ready · reorganizing and deleting remain human work
Can the workflow access our whole Drive?
Only the folders or shared drives you designate. Recording that is part of setup.
Can it edit files?
Only if you configure it. The standard integration reads; writing is a separate, deliberate extension.
Are files copied to Gen8?
What is stored to make them searchable depends on setup. Define it beforehand; your administrator must be able to answer.
Does this work with SharePoint or OneDrive too?
Yes, both have their own integration with the same structure. See Microsoft 365.