Skip to content

Operator: unblock connectors that need live credentials — gdrive OAuth (#246/#239) + Gmail/Granola (#245) #409

Description

@CheeryProgrammer

These could not be verified in CI/sandbox because they need live credentials and, in some cases, an interactive OAuth flow. They need your laptop + accounts.

A. Google Drive import — needs a real OAuth access token (#239 built; #246 = token store)

The gdrive connector exists but needs a valid GDRIVE_TOKEN. Minting/refreshing it is out of scope of the app today (that's #246).

# Obtain a Google OAuth access token with Drive read scope (OAuth playground or your own flow), then:
# .env:
#   GDRIVE_TOKEN=ya29....
docker compose up -d
# trigger: import source=gdrive; confirm a Google Doc / text file becomes searchable.

B. Gmail + meeting-notes (Granola) connectors (#245) — NOT built yet

These connectors don't exist yet; #245 is unimplemented because it needs live creds + product decisions.

  • Decide scope: which mailboxes/labels; Granola account access.
  • Provide test credentials (a throwaway account is fine) so the connectors can be built + smoke-tested against a fake/live API.
  • Note privacy/retention expectations for email content (trust defaults, redaction).
    Comment your answers on Gmail + meeting-notes (Granola) connectors #245 and I (or the team) can implement the connectors blind against a fake API, then you validate with real creds here.

Related: #239, #246, #245.

🤖 Generated with Claude Code

Metadata

Metadata

Labels

area:ingestionIngestion & connectorstype:opsOperations, security, backup, monitoring

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions