Skip to Content

Google Drive Connector

by
Odoo

$ 39.92

v 19.0 Third Party
Versions 17.0 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 1330
Technical Name oe_google_drive_connector
LicenseOPL-1
Websitehttps://odooerp.ae/
Versions 17.0 18.0 19.0

Key Features

Connect Odoo to Google Drive: every record gets its own folder, attachments push as shareable links, with optional storage offload and scheduled auto-sync

OAuth or Service Account

Pick the authentication method per connection: user-consent OAuth or server-to-server Service Account, with multiple connections supported.

Per-record folders

Files are filed under Root / Model / Record in Drive (created on demand), so every record has a clean folder of its own.

One-click push, four ways

Push attachments from the chatter, the attachment form, the kanban card, or in bulk from a list view.

Storage offload

Optionally drop the binary from Odoo after upload; the attachment becomes a Drive link and your database stays lean.

Fetch back on demand

Re-download an offloaded file's binary into Odoo at any time with one click, so the file is right back where you need it.

Auto-push rules

Add per-model rules with an optional record filter (domain) and a connection, so new attachments are pushed automatically.

Scheduled background sync

A built-in scheduled job (Google Drive: Push Attachments) processes auto-push rules on its own schedule.

Shared Drive support

Target a Shared (Team) Drive instead of My Drive, ideal for Service Account connections in Google Workspace.

Searchable activity log

A built-in Activity Logs view records every connect, push, and error, with automatic retention trim to keep it tidy.

Drive Auth Connection
Drive Auth Connection form with Client ID, Client Secret, Root folder name, Authorized Redirect URI and Connect button
Odoo Setting for Default Connection and Offload Binaries to Drive
Odoo Setting for Default Connection and Offload Binaries to Drive form with Default Connection, Offload Binaries to Drive and Log Retention Days fields
Google Drive Connection Menu Form View
Google Drive Connection Menu Form View with Connection Name, Connection Type, Connection Status and Action buttons
Upload to Drive from the chatter
Record chatter showing a message with an attachment and the Upload to Google Drive cloud icon on the message toolbar
Synced Files with state badges
Synced Files list with rows in On Drive and Offloaded state showing Open in Drive and Fetch back actions
Auto-Push Rules per model
Auto-Push Rules configuration with model, optional domain filter, connection and Auto Push toggle
Activity Logs
Activity Logs list showing entries for connects, pushes and errors with a log level filter

User guide

Install the module and Python deps, set up a Google Cloud project, connect Odoo to Google Drive via OAuth or a Service Account, then push attachments manually or let auto-push rules and the scheduled job do it for you.

1. Install

  1. On the Odoo server, install the Python deps: google-api-python-client, google-auth, and google-auth-oauthlib.
  2. Open Apps, remove the Apps filter, and search Google Drive Connector; click Install.
  3. Make sure web.base.url (Settings > Technical > System Parameters) is set to a reachable URL so Google can redirect to /gdrive/oauth/callback.

2. Prepare a Google Cloud project

  1. Go to the Google Cloud Console and create or select a project.
  2. Open APIs & Services > Library and enable Google Drive API.
  3. For OAuth: configure the OAuth consent screen and create an OAuth client ID of type Web application; copy the Authorized Redirect URI from the Odoo connection form.
  4. For Service Account: create a Service Account and download a JSON key; note the service account email.

3. Create a connection in Odoo

  1. Go to Google Drive > Configuration > Connections > New.
  2. OAuth: paste Client ID and Client Secret, set a Root folder name, save, and click Connect to approve in Google.
  3. Service Account: paste the JSON key, enable Use a Shared Drive, paste the Shared Drive ID, add the service account email as a member of that Shared Drive in Google, and click Test Connection.

4. Push attachments

  • From the chatter: hover a message that carries attachments and click the cloud-upload icon.
  • From the attachment form: click Upload to Google Drive in the header.
  • From the kanban: click Upload to Drive on the card.
  • In bulk: select rows in Synced Files or any attachment list, use Actions > Push to Google Drive, and pick a connection.

5. Auto-push, offload & fetch back

  1. Go to Google Drive > Configuration > Auto-Push Rules > New and set the model, optional domain filter, and connection.
  2. Enable the cron Google Drive: Push Attachments under Settings > Technical > Scheduled Actions.
  3. Open Settings > Google Drive to pick the Default connection, toggle Offload binaries to Drive, and set the Log retention in days.
  4. Need a file back in Odoo? Open Synced Files, pick the offloaded row, and click Fetch back.

Frequently Asked Questions

1. How are files organised in Drive?
Files are filed under Root / Model / Record, for example Odoo / Contact / Acme. Folders are created on demand and reused; additional uploads on the same record land in the same folder.
2. OAuth or Service Account, which should I pick?
Use OAuth if you want a real Google account's My Drive to receive the files. Use a Service Account for unattended server-to-server uploads; target a Shared Drive or use Workspace impersonation, because a bare service account has no usable My Drive quota.
3. What is the storage offload option?
When Offload binaries to Drive is on, a pushed attachment leaves Odoo and becomes a Drive link (url type). Your Odoo database stays light while the file remains accessible to users with Drive access.
4. Can I bring an offloaded file back into Odoo?
Yes. Open Google Drive > Synced Files, select the offloaded row, and click Fetch back. The binary is restored as a normal attachment.
5. Is the sync bidirectional?
No. The sync is intentionally one-way from Odoo to Drive. Files created directly in Drive are not imported, and there is no real-time sync; auto-push runs on the scheduled job.
6. Does it support Shared (Team) Drives?
Yes. Enable Use a Shared Drive on the connection, paste the Shared Drive ID, and make sure the authenticating account or service account has access to that Shared Drive.
7. Which Odoo versions are supported?
Dedicated builds are provided for Odoo 17.0, 18.0, and 19.0, on Community and Enterprise editions. The Python core is shared across the three.
Module Support & SLA
For support related to this module, contact apps@odooerp.ae
Standard response time (SLA) for support queries is typically 1 to 2 working days.
+971 54 289 8664 Email Us
Oakland partner and services
Support and contact information
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 1330
Technical Name oe_google_drive_connector
LicenseOPL-1
Websitehttps://odooerp.ae/ 
Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.