Connect Google Drive
Last updated: May 19, 2026
Connect Google Drive
Wevion connects to Google Drive via a Service Account (NOT user OAuth — verified in apps/backend/src/lib/google-drive.ts). The service account uses GOOGLE_SERVICE_ACCOUNT_EMAIL + GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY env vars with scope https://www.googleapis.com/auth/drive. You share specific folders with Wevion's service account email — Wevion can only access what you share.
Who is this for
Creatives and mediabuyers who want to:
Auto-sync creative assets from a Drive folder into Creative Hub
Source brief documents from Drive for campaign generation
Maintain Drive-based asset libraries shared with Wevion
How Drive auth differs from other integrations
Most Wevion integrations use user OAuth (you authenticate your Meta/Google Ads/Shopify account). Drive is different:
Service Account model: Wevion has a server-side service account with its own Google identity
You share your folder with that service account email (like sharing with a colleague)
Wevion can only access what's explicitly shared — never your entire Drive
Benefits:
No browser OAuth flow needed
No token expiry (service account credentials managed by Google)
Scoped to specific folders (security)
No "user not available" issues (service account is always available)
Before you start
A Google account with Drive access
The folder you want Wevion to access in your Drive
Wevion role: manager, admin, owner, super_admin
How to connect
Step 1: Open the Drive connector page
In sidebar click Connect → Google Drive or visit /connect/drive. Wevion shows:
The service account email to share folders with (e.g.
wevion-drive-sa@wevion-prod.iam.gserviceaccount.com)Status: not yet shared / N folders shared
Step 2: Share your folder with Wevion's service account
In Google Drive:
Open the folder you want Wevion to access
Click Share (top right of folder)
Paste Wevion's service account email
Set permission level:
Viewer = Wevion reads files (one-way sync into Wevion)
Editor = Wevion can also write back (derived assets, processed outputs)
Click Send (don't worry about notification — Wevion's service account doesn't read email)
Step 3: Confirm in Wevion
Back in Wevion's /connect/drive:
Wevion polls for shared folders every 5 minutes
Once detected: folder appears in the connected folders list
You can rename it for Wevion-side display, set folder type (creative source / brief source / general)
Step 4: Configure folder usage
For each shared folder, pick its purpose:
Creative source: files auto-imported to Creative Hub on detection
Brief docs: files indexed for AI campaign generation (Wevion reads docs as input)
General: accessible via Wevion's file picker for various uses
Step 5: First sync
Wevion polls every 5 minutes for new files in shared folders. First poll after configuration brings existing files into Wevion.
Service Account details
Service account ID format: [name]@[project].iam.gserviceaccount.com
The exact email depends on your Wevion deployment. Check /connect/drive for your instance's service account email.
If env vars not configured (GOOGLE_SERVICE_ACCOUNT_EMAIL or GOOGLE_SERVICE_ACCOUNT_PRIVATE_KEY missing), Drive connector returns an error: "Google Drive credentials not configured." Contact support@wevion.ai to enable.
Folder permissions explained
Permission level | What Wevion can do |
|---|---|
Viewer | Read file metadata + content (download for processing) |
Editor | Plus: create derived files (resized images, normalized videos), update existing files Wevion created |
Commenter | Not used by Wevion — pick Viewer or Editor |
For most use cases: Viewer is sufficient. Use Editor only if you need Wevion to write back to your Drive.
What's accessible
Wevion only sees:
Files in folders you explicitly shared with the service account
Sub-folders of those folders (recursive)
File metadata (name, type, size, created/modified timestamps)
File content (downloaded when Wevion needs to process)
Wevion does not see:
Your other Drive content (not shared with the service account)
Other users' files
Your Gmail, Calendar, Contacts, or any other Google service
Use cases
Creative Hub sync
Most common use:
Share a "Wevion Creative Library" folder with Editor permission
Files added to this folder auto-import to Creative Hub within 5 min
Wevion organizes by file type (images / videos / audio)
See com-113 for folder management.
Brief doc ingestion
For AI campaign generation:
Share a "Briefs" folder
Drop campaign brief documents (Google Docs, PDFs, etc.)
Wevion indexes via campaign-by-context populator (
apps/backend/src/services/campaign-by-context/populator-drive-client.ts)AI generators can reference brief content when generating campaigns
General asset sharing
For team-wide assets (logos, templates, brand guidelines):
Share a "Brand Assets" folder
Available via Wevion's file picker in Creative Hub / Campaign Creator
Multiple Drive accounts (multi-tenancy)
For agency use cases: each client's Drive can be shared with Wevion's service account independently. Wevion treats each shared folder as its own data source. No conflict between clients.
Removing access
To revoke Wevion's access to a folder:
In Google Drive: open folder → Share → remove Wevion's service account email
In Wevion: folder disappears from
/connect/drivewithin 5 min
Files already downloaded by Wevion remain in Wevion's storage (per data retention policy) but no new syncs occur.
Security
Service account private key stored encrypted at rest in Wevion's secret manager
Audit log records every Drive API call (admin view)
File access scoped to shared folders only (Google enforces at Drive API level)
No PII or sensitive Wevion data uploaded to Drive (one-way: Drive → Wevion)
What you'll see
After successful share + connect:
Connector card: green Connected badge
N folders shared listed
Files appearing in Creative Hub / Brief library / file picker depending on folder config
Toast: "Drive folder synced — N files imported"
Common issues
"Drive credentials not configured": env vars missing on Wevion's backend. Contact support.
Folder shared but not appearing in Wevion: 5-min sync delay. Verify share permission level (Viewer or Editor — not Commenter).
Files not auto-importing to Creative Hub: folder type set to "general" not "creative source". Update folder config.
"Permission denied" when Wevion tries to write back: folder shared as Viewer (read-only). Change to Editor.
Service account email rejected by Google Drive Share: format issue or temporary Drive bug. Copy-paste cleanly, retry.
Need to share many folders: you can share whole parent folder + Wevion sees sub-folders recursively. Avoids many shares.
Related
Drive creative folder management — folder organization for Creative Hub
Upload your first creative to Creative Hub — Creative Hub basics
Integrations overview — full integration catalog