Skip to content
Call wiki

How fresh is a Google Drive doc when Claude reads it through the connector?

Last updated 2026-08-17 · Confidence: documented — Anthropic’s help center and connector docs, read that day; the upload-snapshot claim is inferred, underlined.

Per Anthropic’s docs: connector reads are live tool calls with no Anthropic-side index, and Google Docs added to chats or projects “sync directly from Google Drive, so you’re always working with the latest version” — while non-Drive files you upload have no documented sync at all.

Connector reads are live

Section titled “Connector reads are live”

Anthropic’s enterprise search article is explicit about the mechanism: “No data from connected services are indexed in our systems for serving queries” — “Search results are generated by making MCP calls.” When Claude searches or reads Drive through the connector, it issues a tool call against Google’s API at request time; there is no Anthropic-side crawl schedule to lag behind. A recurring task that reads the doc via connector tools on each run therefore sees whatever Drive returns at that moment.

Docs added to a chat or project sync

Section titled “Docs added to a chat or project sync”

For Google Docs attached via “Add from Google Drive”, the Google Workspace connectors article says they “sync directly from Google Drive, so you’re always working with the latest version,” and that after you edit, “the document continues to sync with the most up-to-date version in Google Drive.” The Drive integration docs page lists “Live sync: Documents continue syncing with the latest Google Drive version.” Neither page states the sync’s granularity (per message vs. background interval), only the guarantee of the latest version. Drive-synced knowledge works only in private projects, Google Docs only (no Sheets/Slides), text up to 10MB, no images or comments.

Uploaded files: no documented sync

Section titled “Uploaded files: no documented sync”

For plain uploads (PDF, DOCX, etc.) to a chat or project, neither the upload files article nor the projects article documents any update behavior. The safe assumption is snapshot-at-upload. To refresh an upload, remove and re-add it.

Forcing freshness

Section titled “Forcing freshness”

No manual “re-sync” control is documented; freshness is automatic for Drive docs and connector calls. For a recurring summarizer (say, an hourly scheduled task): keep the planning docs as Drive-synced docs or have the task fetch them by URL through the connector each run — not as one-time uploads. To confirm on your own plan, run the two-minute test: edit a synced doc, immediately ask Claude in a fresh message for the doc’s last line, and repeat for an uploaded copy.

Sources

Section titled “Sources”