Connectors
PlatformDefinition
Integrations that let Claude work with content in an external source (e.g., Google Drive, Gmail) where it already lives, rather than requiring a manually exported and uploaded copy. Distinct from uploads (static files added directly); connector availability depends on the plan/pricing tier and is not universal.
Example Usage
Connect Claude to the team's Google Drive so it can reference the latest version of a shared planning document directly, instead of someone re-exporting and re-uploading the file every time it changes.
In Depth
Two Paths to Knowledge
Knowledge reaches Claude through two distinct paths:
| Path | What it is |
|---|---|
| Upload | A file added directly, becoming a static snapshot of Project or conversation knowledge |
| Connector | An integration to an external source (Google Drive, Gmail) letting Claude work with content where it already lives |
An upload is a copy as it existed at the moment it was added; a connector instead points at a live source, so Claude works with the current version rather than whatever someone happened to export.
Availability Is Plan-Dependent
Which connectors are available is tied to the account's plan or pricing tier -- it is not a capability every account has by default. Assuming a connector such as Google Drive or Gmail is universally available, rather than checking the current tier, is one of the most common mistakes in configuring knowledge sources.
Curation and Governance Still Apply
A connector doesn't need the same mechanical curation as an upload (it points at a live source rather than accumulating stale copies), but the decision to connect it at all -- and to which folders or scopes -- is itself a curation and governance choice. Because connected content may include sensitive or regulated data, turning on a connector is a data-handling decision, not merely a convenience decision, and should be checked against organizational policy before it's enabled.
Common Pitfalls
- Assuming every connector (Google Drive, Gmail, or others) is available on every plan.
- Treating an upload and a connector as interchangeable, missing that a connector reflects a live source while an upload is a fixed snapshot that can go stale.
- Enabling a connector to sensitive data without checking whether policy permits it, on the assumption that a connector is purely a technical convenience.