Google Drive
Link Google Drive files to any deal, account, or contact without copying bytes. Permissions stay with Google so viewers only see what they already have access to. Agents can list and read docs when answering questions on the record.
Everything Google Drive does inside Strkr.
- Attach Drive files to any record
- Permissions respected via Google
- Agent-readable context on records
- Workspace-wide or per-user connect
Native code, not a shim.
OAuth where available
Google Drive will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Shared by the workspace
A workspace admin connects Google Drive once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Google Drive from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Google Drive is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Google Drive is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.