Skip to main content

Google Drive

The Google Drive integration lets you push documents and email attachments into Drive — pick or create a folder and upload, on demand or from a workflow.

Drive is a separate Google app from Gmail. The interactive export uses Google's restricted full drive scope (so you can browse and write to any folder), which must be its own OAuth client — distinct from the one used to connect a Gmail mailbox. Its callback is /oauth/google/callback.

What you can do​

  • Send to Drive from a document — browse your Drive, create a folder if needed, and upload the file.
  • Upload attachments from an email to a Drive folder (interactively, via Cmd+K or Scout, or from a workflow).
  • Auto-archive documents to a configured folder as they're processed.

Setup (self-hosting)​

  1. In the Google Cloud Console, create an OAuth client (a separate client from your Gmail one, ideally in its own project).
  2. Add the scope https://www.googleapis.com/auth/drive and the redirect URI <your-app-url>/oauth/google/callback.
  3. Set the credentials in your environment: 
    GOOGLE_DRIVE_CLIENT_ID=your_client_id
    GOOGLE_DRIVE_CLIENT_SECRET=your_client_secret

Because the full drive scope is a Google restricted scope, the OAuth consent screen must pass Google verification before you use it in production. Accounts connected under the older drive.file scope need to reconnect to gain full-folder access.

Connecting and using it​

  1. Go to Settings → Integrations → Google Drive and connect your account.
  2. Open any document and click Send to Drive, choose a folder (or create one), and upload.
  3. To automate it, add a Send to Google Drive action to a workflow — the file source is the triggering email's attachments.
Last updated on