IntegrationGoogle Drive

Only the Drive files you pick, always in sync.

Connect Google, choose documents in the Picker, and Odin keeps exported copies updated for your project wiki.

  • No full-drive access; explicit file selection
  • Auto-refresh when linked files change
  • Docs, Sheets, Slides, and PDFs normalized for ingest
All integrationsHow Odin works

In Odin

Saved snapshot (Raw)
Yes
Live in chat
No
How it works

From connect to project knowledge

  1. Connect with Google OAuth using drive.file scope (not full Drive read).
  2. Use the Google Picker in Integrations to select Docs, Sheets, Slides, PDFs, or plain text.
  3. Sync exports snapshots to Raw and re-runs when Drive sends change notifications.
  4. Ingest queues after sync like other sources.
  5. Chat uses wiki and indexed Raw only. No browse-all-of-Drive tool.
Why Odin

Why Google Drive makes Odin better

  • Specs and PRDs that live in Drive become first-class wiki inputs without manual export every week.
  • Least privilege: Odin never sees your whole Drive, only files you explicitly choose.
Project wiki

Part of one compounding knowledge layer

Odin maintains a persistent project wiki that compounds over time. Integrations write to Raw, ingest and compile turn that into durable linked knowledge, and chat answers using the wiki first with live tools when freshness matters.

Google Drive

PRDs and one-pagers stop living outside the project brain.

Connect Google Drive under Project → Integrations. Odin saves what you choose, turns it into project knowledge, and answers in chat using what is connected.

All integrationsHow Odin works