Google Drive integration

What connects

The connection uses Google OAuth 2.0 with the Google Drive API's read-only scope, plus OpenID and email to identify the connected account. IntellaOne can list folders and read files within the folders selected for sync; it does not write to Drive.

• An IntellaOne administrator configures a Google Cloud OAuth web client, enables the Google Drive API, and adds the server callback and client credentials.
• The connected Google user grants the requested read-only access, then chooses which visible folders IntellaOne may sync.
• Folder selection is the source boundary. Access to other Drive files does not make them available to this connection.

Information used

IntellaOne traverses the selected folders, including nested folders within the provider and sync boundaries, and turns supported document text into citable knowledge sources. A document's Drive link is retained when the provider supplies one so an answer can point back to the source.

• Google Docs and Slides are exported as text; Google Sheets are exported as CSV.
• PDF, Word, PowerPoint, Excel, and text files are downloaded and passed through the supported text-extraction path.
• Images, video, archives, unsupported Google file types, and other unextractable files are skipped rather than presented as searchable text.
• Only files in enabled selected folders are considered; a file outside that selection is not imported merely because it exists in the connected Drive.

Why it is useful

Teams can bring the documents they choose into conversation context and let IntellaOne cite the source behind a retrieved answer, without creating an unrestricted mirror of the connected Drive.

• A selected document can supply context during a live conversation.
• The connector's source link helps a rep trace an answer back to the Drive document when a link is available.
• Selection is not a team-review signal: review, governance, and approval remain team decisions outside the folder picker.

How the workflow behaves

Google Drive syncs on the catalog's scheduled 30-minute cadence rather than serving a live Drive mirror. New and changed files are fetched for extraction; unchanged files are not downloaded again.

• When a completed provider listing shows a file has disappeared from every selected folder, reconciliation removes its connector source so it stops surfacing in answers.
• Large or deeply nested folders can result in bounded imports; unvisited files are not treated as deleted.
• The sync is bounded at 300 files per selected folder per run, 10 list pages per folder, and five nested folder levels. Choose smaller folder selections when you need an easier import to check, and check expected documents for missing items after sync.
• A folder or file API error can interrupt or partially complete a run, and Google Drive rate limits or authorization changes can require a later retry.

Prerequisites and limits

An IntellaOne administrator must configure the Google Cloud OAuth client, callback, Google Drive API, and server credentials. The connected Google user must authorize read-only Drive access and select at least one folder. Provider permissions, account configuration, unsupported file types, and the bounded traversal limits determine what can be imported.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Security and privacy boundaries

Newly saved connector credentials are encrypted before storage.

Connected tools sync server-side under the user's own credentials. Requested permissions and data flows are connector-specific.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Google Drive access is read-only in this integration: IntellaOne performs no Drive writes. The selected-folder list and its enabled state control which documents can enter the knowledge pipeline; a transient, incomplete listing does not remove previously synced sources.

• The connection does not read the entire Drive by default.
• Selection makes a document available to the connector; it does not automatically certify, review, or approve the document's contents.
• A successful read depends on Google accepting the authorized request and the connected account retaining access to the selected folders.

Frequently asked questions

Does selecting a Google Drive folder mean the team reviewed its documents?

No. Selection defines which documents can sync into IntellaOne's citable context. Team review, governance, and approval are separate decisions and are not inferred from the picker.

Can IntellaOne change files in Google Drive?

No. This connector requests read-only Drive access and does not create, edit, move, or delete Drive files.

Which Google Drive files can become context?

Google Docs, Slides, and Sheets use provider exports, while supported PDF, Office, and text files use the extraction path. Unsupported or unextractable file types are skipped.

What happens when a Drive folder is large?

Imports are bounded per run and may cover only a subset of a large or deeply nested folder. Choose smaller folder selections when possible and check expected documents for missing items; unvisited files are not treated as deleted.