Skip to main content
Coeffection

Google Drive Integration

Attach Google Drive files to any record (Contact, Lead, Opportunity, custom entity) and store inline images from rich-text custom fields in your Drive workspace. Coeffection never stores the file bytes — only a reference to the Drive file ID and a signed URL fetched on view.

Prerequisites#

  • Google account (personal or Workspace) with access to the Drive folder you want files written to.
  • Coeffection role with integrations:manage permission (typically Admin).
ℹ
If you already connected the Google (Gmail & Calendar) integration, Drive uses the same OAuth connection — re-consent only adds Drive scopes, no new account needed.

OAuth scopes#

Coeffection requests three Drive scopes on first connection:

  • drive.file — read/write only files Coeffection creates or you explicitly pick. Coeffection cannot see your other Drive files.
  • drive.readonly (optional) — required only if you want the Drive folder picker to browse your existing folders.
  • drive.metadata.readonly — used to fetch file names/icons for the file picker.

Connecting Google Drive#

  1. Go to Admin Settings → Integrations → Google Drive.
  2. Click “Connect Google Drive”.
  3. Sign in with the Google account that owns the target Drive workspace.
  4. Approve the requested scopes.
  5. Pick a default folder for uploads (or accept the auto-created “Coeffection” root folder).

Attaching Drive files to records#

Records that have a Drive File custom field can store one or more attached Drive files. To add an attachment:

  1. Open any record (Contact, Lead, Opportunity, etc.).
  2. Find the Drive File field (custom field type configured by your Admin).
  3. Click “Add file” → the Google Drive picker opens in a modal.
  4. Pick an existing file OR upload a new one from your computer (uploaded files land in the default folder you picked at connection time).
  5. Attached files appear as chips with name, icon, and size.

Inline images in rich-text fields#

When a Rich-Text custom field is configured with Drive as the image provider, dragging or pasting an image into the editor uploads it to your chosen Drive folder and inserts a reference. See Rich-Text Fields for the editor walkthrough.

ℹ
Pick a dedicated Drive folder for Coeffection uploads (e.g., “CRM Images”) so future cleanup is easy. The default “Coeffection” folder is fine for most teams.

Permissions & sharing#

  • Files uploaded by Coeffectionare shared as “anyone with the link” by default so any Coeffection user viewing the record can fetch the file. You can tighten this in Drive (Share → Restricted) after upload, but the file will only render in Coeffection for users who also have Drive access to it.
  • Files attached from your existing Drivekeep their existing sharing rules — Coeffection doesn't change them.
  • Image bytes never touch Coeffection servers — the editor fetches a signed URL from Drive at render time.

Troubleshooting#

“Provider unavailable” in the rich-text editor

The Drive integration is not connected, OR the rich-text field isn't configured to use Drive as its image provider. Check Admin Settings → Integrations → Google Drive, then verify the custom field's “Image storage” setting.

Picker shows no folders

Coeffection requested the drive.file scope only by default. Re-consent with the optional drive.readonly scope to enable folder browsing (Admin Settings → Integrations → Google Drive → “Reconnect with full picker”).

Inline image shows broken icon on a shared record

The viewer's Google account doesn't have access to the Drive file. Open the file in Drive and add the viewer's account, or change sharing to “Anyone with the link”.

⚠
Coeffection respects Google's API quotas. If your tenant uploads more than ~1,000 files per day, contact support — we can negotiate a higher quota with Google on your behalf.