Guru and Google Drive: Connect Documents to Team Answers

Connecting Google Drive to Guru lets your team link knowledge cards directly to the source documents they are based on, so readers can see the original material without asking where it lives. Guru can also suggest Drive documents when someone asks the AI search feature a question. Tools like fenbs complement this by keeping the decisions your team makes about which documents are the approved source of truth alongside the tasks that rely on them.

What Guru's Google Drive integration does

The integration lets Guru index content from connected Google Drive folders so it can surface those documents in AI-powered search results. You can also insert Drive links into cards as related resources, and Guru shows a preview of the linked file without the reader having to leave the card. This keeps a card concise while giving readers a path to the full source.

Guru does not copy the content of Drive files into its database. It indexes and links them. If a file is deleted or moved in Drive, the link in the Guru card will break. That makes it important to check the connection status occasionally and to update cards when a source document is reorganized.

Set up the Google Drive integration in Guru

1. Log in to Guru as a workspace admin and open Settings > Integrations.
2. Find Google Drive in the integrations list and click Connect. You will be asked to sign in with a Google account and approve the requested permissions.
3. Choose which Drive folders or shared drives Guru should index. Start with a narrow scope, such as a single shared folder, rather than granting access to all of Drive.
4. Once connected, test the integration by searching for a term you know appears in one of the indexed documents. Confirm that the Drive file appears in the results.
5. On any Guru card, use the Related Resources section to add links to Drive documents that support that card's content.

The Google account used to connect Drive becomes the integration's access credential. Files that account cannot see in Drive will not be indexed. If your most important documents are in a shared drive where that account is not a member, add it as a viewer before setting up the integration.

Check document access before syncing

Guru respects the Drive permissions of the account used to connect. But if a reader in Guru clicks a link to a Drive file they do not have direct access to in Google Workspace, they will see a permission denied error when they open the file, even though the link appeared in search results. Review the intended audience for each linked document and confirm their Drive access before you add the link to a card.

For sensitive documents such as contracts, HR policies, or financial records, consider whether Drive is the right place to surface them through Guru at all. Linking a sensitive file from a general-purpose knowledge card may expose it to more people than intended. A more controlled approach is to summarize the key points in the card and link only to a summary document rather than the original.

Keep cards current as documents change

Guru cards have a verification cycle: owners are prompted to review cards on a schedule and mark them as verified. Add the verification date to your calendar if you manage cards that rely on frequently changing Drive documents. When a linked document is updated, check whether the card's summary still accurately reflects the current content.

See integration testing for a framework to test connected tools when something changes. When you update the Drive folder structure, re-test the Guru search results for the most important terms to confirm the indexed content is still accurate.

What the integration does not cover

Guru does not automatically update card content when a linked Drive file changes. The card owner must manually review and revise the card. Guru also does not support two-way sync: you cannot push changes made in Guru back to Drive documents. If your team edits both the Drive source and the Guru card independently, the two can drift apart over time. Designate one as the primary record and use the other as a link or summary.

How to do this with fenbs

1. Create a free account and add a project for the knowledge base work.
2. Add a Links and listings entry for each key Google Drive folder or document your team treats as an approved source.
3. Record decisions about which documents are authoritative for specific topics as Decisions and rules, so the next person reviewing a Guru card knows what the team already agreed on.
4. Add a task for each card that needs to be updated when a Drive source changes, and move it through the kanban board as it is reviewed and verified.
5. Connect a supported AI assistant from Integrations to help draft card content or check that it aligns with the linked Drive source.

fenbs does not connect to Guru or Google Drive directly. It keeps the decisions about which documents are approved sources, and the tasks for maintaining accuracy, in a single record outside either tool. For connecting an AI assistant to Google Drive files directly, see Google Drive MCP.