Answer questions with source references
An answer from your own documents, referencing the document and its specific location.
Gen8
Source: Connecting documents and knowledge
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: configured
The knowledge people seek usually already exists: in a document library, shared folder or handbook nobody opens anymore. This integration makes those documents useful as workflow sources, so an answer comes with a reference rather than out of nowhere. Source-system permissions remain authoritative.
At a glance
Route: configured
Components: SharePoint, Google Drive, OneDrive
Capabilities
The workflow reads documents from your designated sites, libraries and folders and uses them as sources:
Google Drive goes beyond files: its own Google Docs, Sheets and Slides tools let a workflow read and edit content instead of merely referring to it.
What does not happen: moving, deleting or reorganizing documents. Cleanup is human work; this integration provides access, not reorganization.
Inspiration
A few examples of work you can hand over through this integration. We work out what fits your organisation together during scoping.
An answer from your own documents, referencing the document and its specific location.
Two versions of a contract or proposal side by side, with differences identified.
Data needed by a next step is extracted from the document.
If designated sources do not contain the answer, the workflow says so rather than inventing something.
A workflow can also build a report with Google Docs. A change starts as a proposal.
Figures from documents enter a Google spreadsheet, first visible as a proposal, then logged.
Permissions and data
An administrator configures the connection with access to designated sites, libraries or folders — not the entire environment. Scope is the most important setup decision.
The principle is that source-system permissions remain authoritative: a document-access workflow must not become a way around them. How strictly that works depends on access configuration and the identity used by the integration. This must be explicitly recorded and checked during setup, not taken for granted.
Control
Reading documents as sources is read only and requires no approval per question. Approval comes earlier: selecting sources and deciding who may use the workflow.
That changes when a workflow also writes in documents — generating a report or updating a spreadsheet. A change must then first be visible as a proposal, and every step logged. Processing takes place in the EU.
Evidence
SharePoint, Google Drive and OneDrive each have their own Gen8 integration: SharePoint tools for sites, lists and files; Drive tools for files, Docs, Sheets and Slides; OneDrive tools for files — see also Microsoft 365. The route is configured because value depends entirely on the sources an administrator designates. For storage without its own integration, see MCP, API and custom development. Related workflows: making documents accessible as knowledge and querying a knowledge base.
Answer a question from designated sources
That must never be the result. Source-system permissions should remain authoritative; how that works in your environment must be checked during setup rather than assumed.
The workflow says it is not in the designated sources. That is a useful answer; an invented answer is not.
Exactly what is stored to make them searchable depends on setup. Define it beforehand — your administrator must be able to answer before the integration is enabled.
Not through a ready-made integration. It requires a custom route; see MCP, API and custom development for what is involved.