v 16.0 Third Party 110
Live Preview
Included Dependencies
Lines of code 6681
Technical Name google_drive_odoo
LicenseSee License tab
Websitehttps://faotools.com/apps/16.0/google-drive-odoo-integration-741
Also available in version v 11.0 v 15.0 v 13.0 v 14.0 v 12.0 v 10.0
You bought this module and need support? Click here!
Included Dependencies
Lines of code 6681
Technical Name google_drive_odoo
LicenseSee License tab
Websitehttps://faotools.com/apps/16.0/google-drive-odoo-integration-741
Also available in version v 11.0 v 15.0 v 13.0 v 14.0 v 12.0 v 10.0

This is the tool to integrate Google Drive features with Odoo folders and files. The app automatically stores Odoo attachments and directories in Google Drive and provides instant access to them via web links.

This is an extension to the tool Cloud Storage Solutions. Read the full description of the features and optional modules on the core module page.
Synchronize Odoo folders with Google Drive

Automatic folders' structure

Decide which Odoo document types should have their own folders trees and synchronize those to Google Drive

Automatic regular sync

Rely on auto-synchronization between Odoo and Google Drive based on scheduled jobs. No manual interaction is required

Bilateral sync

Odoo sends attachments to Google Drive and retrieves files from there. Binary content is kept in clouds, while Odoo provides direct access to synced items

Cloud synchronization history

Control Google Drive sync logs right in Odoo. Export and share those in case of any issues. Be notified of any client disconnections

File manager interface

Manage synced folders and attachments from a single Odoo view. Comfortably navigate by directories. Search and download files one by one or in batch. Upload and move attachments to folders

Attachment box

Organize files of any Odoo object in a set of subfolders. Instantly access folders and files in the attachment box and in Google Drive.

Document-related folder in Google Drive
Google Drive: sync attachments
Google Drive subdirectories
Odoo's root folder is in Google Drive

Excellent !!!

Great App and great Service from faOtools.

-- Carlos A. Villarreal C.

Best module for integration with google drive

The module performs its function correctly and faOtools responds quickly to any problem and, in case of detecting any bug, quickly apply the changes. Its support is 10 stars.

-- sistemas@deza-sa.com

How synchronization works

Automatic two-sided sync

  • Configure sync for one or multiple Google Drive instances
  • Integration is based on scheduled jobs and is fully automatized. The app regularly checks changes in systems and runs sync operations
  • Synchronization is bilateral. Updates in Odoo are reflected in Google Drive (direct sync); changes in Google Drive modify Odoo folders and attachments (backward sync)
  • Cloud connection with Google Drive might be reset. In this way, the app assumes getting back all items back to Odoo (reverse sync)
  • Odoo folders and attachments might be re-attached to a new cloud client from Google Drive. Hence, items will be first taken back to Odoo (reverse sync) and then will be put into the new cloud storage (direct sync)

Queue-based synchronization

  • Once in 15 minutes, the app examines updates in Odoo and Google Drive to prepare a synchronization queue
  • Folders' checks follow the First-In-First-Out (FIFO) principle. So, directories that have not been examined for the longest will be processed first
  • Once in 15 minutes, the sync queue is run by the special scheduled job. Firstly, the most important (blocking) tasks would be done
  • Control planned jobs and their fulfillment in the special Odoo logs interface (Cloud Storage > Configuration > Sync Logs). Subscribe for particular cloud clients notifications
  • If the app faces sync failures, it will re-try operations afterward. Sync queue processing would not be stopped if there are items not blocked by such failures

Odoo attachments for Google Drive: direct sync

  • Direct sync prepares the folders' hierarchy and uploads Odoo attachments for Google Drive
  • Direct sync checks whether attachments are added or deleted for synced directories. If so, they will be created in Google Drive or removed from there. In particular, it means that any file added to a folder-related Odoo object (e.g. Quotation), would be automatically moved to a linked cloud client
  • Direct sync makes all synced Odoo attachments change their type to a link (URL), while binary content is removed with one of the next Odoo cleaners. So, no actual files would be stored on your Odoo server
  • Direct sync checks whether a new folder is added. Disregarding whether it is done manually or automatically, the app would generate a peer directory in Google Drive
  • Direct sync checks whether there are any updates in folders. If so, such changes are reflected in Google Drive

Google Drive files and folders for Odoo: backward sync

  • Backward sync checks whether any files or subfolders are added to Google Drive folders. If so, the app would create URL attachments/subdirectories inside linked Odoo directories (and hence Odoo objects if any)
  • Backward sync checks whether there are any updates in folders or attachments. Such updates would be then reflected in Odoo
  • Backward sync checks whether any files are deleted/moved in a Google Drive document folder. If so, a linked Odoo attachment would be also unlinked or moved
  • If you deleted a Google Drive folder related to a folder rule / Odoo object, their child files would be deleted as well. Thus, Odoo would remove related attachments. The folders, however, will be recovered with a direct sync
  • In case of conflicts, direct sync changes are in general considered more important than backward updates.

Resetting or changing Google Drive: reverse sync

  • In case you decided to reset the connection with Google Drive, files would be moved back to Odoo
  • In case you decided to change the cloud client of a folder rule or a folder, files would be first taken back to Odoo, and then direct sync for a new client would be done
  • Reverse sync operations are prioritized to direct and backward sync operations
  • Not all items can be correctly reversed to Odoo due to cloud client peculiarities. For example, there are documents that may exist only in cloud storage environments (e.g. Google Sheets). The app would try to convert such documents, but in some cases, it will require manual interactions.
  1. Turn on the option 'Google Drive Sync' (cloud Storage > Configuration > Configuration). The optional add-on Google Drive Odoo Integration is required
  2. Go to the Google Developer Console via the URL https://console.developers.google.com
  3. Select or create a project
  4. Find the section 'Dashboard' and press 'ENABLE APIS AND SERVICES'
  5. Find Google Drive API and push the button to enable its API
  6. Go to 'Credentials' and press the button 'Configure Consent Screen'. As the User Type select 'External' and push 'Create'
  7. Add app information
    • As an app name select any suitable
    • As a user support email and developer contact information, select your email address
    • Press 'Save and Continue'
    • Avoid adding any other details except the ones named here (especially, a logo or authorization domains). This will invoke a long and complex Google verification process that is of no actual need to you
  8. On the 'Scopes' page just press 'Save and Continue'
  9. As Test Users add your GMail email address, then press 'Save and Continue'
  10. Then, go to Credentials and push the button 'Create Credentials'
    • 'Web application' as the application type
    • As the authorized redirect URI, add the link in a format [YOURODOOSITENAME]/google_drive_token (e.g. https://odootools.com/google_drive_token).
    • Save the app and copy 'Client ID' and 'Client Secret'
  11. Publish the app on the OAuth consent screen. Otherwise, the token will be expired every week
  12. Go to Odoo Cloud Storage > Configuration > Cloud Clients press 'Create'
    • As a reference, introduce any name which would be clear to all users
    • As a Cloud client, choose 'Google Drive'
    • As a Root folder name, enter a title that will be used as the parent Google Drive directory for all synced folders. For example, 'Odoo' or 'OdooERP'
    • Copy 'Client ID' to the 'App client ID'
    • Copy 'Client Secret' into the field 'App client secret'
    • Insert previously generated redirect URL
    • If you use team drives, check the related box. Make sure you really use team drives. In your Google Drive you should find the item 'Team Drives' in the left sidebar. This feature is available only for business and enterprise tariffs
    • If the option 'Team Drive' is enabled, introduce its name. It should be absolutely the same as you see it in your Google Drive. Make sure that your user has full rights to all Google drives (usually, it is the same user who configures your team Google Drive)
  13. Press 'Confirm'. Odoo redirects you to the Google login page. Check in the system, agree with all conditions, and grant all permissions asked
  14. After login, Google redirects you back to Odoo. Google Drive - Odoo synchronization is ready to be done
  15. Apply the newly created cloud client to folder rules and/or manual folders which should be synced to that Google Drive
  16. Await the sync scheduled job to be started. For testing purposes only: trigger integration manually from Cloud Storage > Configuration > Configuration > the button 'Launch sync'.

Google Console: APIs

Google Console: the list of APIs

Find the Google Drive API

Finding the Google Drive API

Enable Google Drive API

Enabling Google Drive API

Configure the Google Consent Screen

Configuring Google Consent Screen

Set the External User Type API up

Setting up External User Type API

Enter Google app details

Entering Google app details

Define Google app scopes

Google app scopes

Add authorized users

Adding Google-authorized users

Registering Google app credentials

Creating Google app credentials

Introduce a Google Drive app redirect URL

Google Drive app redirect URL

Publish the app to avoid too frequent token expiration

Publishing the Google API app

Copy the app credentials

Google app credentials

Enter Google app credentials to Odoo

Google app credentials in Odoo

The app itself does not regulate access rights on the Google Drive side. It should be done manually there. Thus, Odoo would create target folders in Google Drive, which by default are not shared, while you can change permissions to any of the folders. For example, to grant full rights for the 'Odoo' directory or to a specific 'Odoo > Sale Orders'  or 'Odoo > Sale Orders > SO-001'.

The app works on a single user endpoint principle. So, all sync operations are done under the same Google Drive user (according to the Google API app you have configured).

To delete a file completely, you need to clean the bin in Google Drive as well.

Also, keep in mind that a file might still be in Odoo, because the backward synchronization doesn't proceed the attachment yet. As this is a scheduled process, some time is required.

The module uses only free API, so you will not be charged by Google.

The app assumes that the binary content of attachments is kept in Cloud Client instead of the Odoo server. So, such attachments in Odoo become of the URL type, and you may any time access them either from the attachments box or from the Cloud Client.

After the setup, no manual actions are required, as the synchronization is fully automatic. Just decide which Odoo document types should be synced and set up a related model to sync for each of those (Customers, Sale or Purchase Orders, Tasks, Projects, etc.).

Yes, you can. To that goal, prepare a rule for each, and then those apply filters: for example by type of a project.

Try to make filters self-exclusive in order a document can be definitely assigned. For instance, 'customer but not supplier', 'supplier but not customer'. Otherwise, a specific document folder would jump from one model to another.

No. We have strong reasons to avoid real time sync:

  • Performance issues. In case a sync is real time, each file upload will result in the loading screen.

  • Conflict issues. If 2 users simultaneously change an item, it might lead to unresolved situations. In case of regular jobs we can fix it afterwards, while in case of real time we would need to save it as some queue, and it will be even more misleading for users.

  • Functionality issues. In particular, renaming and restructuring of items. In the backward sync the tool strictly relies upon directories' logic, and during each sync 100% of items are checked. In case it is done after each update, it will be thousands of requests per second. If not: changes would be lost.

Yes, although in case of many folders / attachments to sync, the process might be slow. Simultaneously, our clients reported to us the environments with >10k partners and ~5k product variants to be synced, and the processes were acceptable.

A few points to emphasize:

  1. The sync is constructed in such a way that anyway any item will be synced and will not be lost, although it might be not fast. It is guaranteed by first-in-first-out queues and by each job commits.

  2. The number of objects might be limited logically. The models' configuration let you restrict sync of obsolete items (e.g there is no sense to sync archived partners or orders which are done 2 years ago).

According to the current Odoo Apps Store policies:

  • every module bought for the version 12.0 and prior gives you an access to the all versions up to 12.0.
  • starting from the version 13.0, every version of the module should be purchased separately.
  • disregarding the version, purchasing a tool grants you a right for all updates and bug fixes within a major version.

Take into account that faOtools team does not control those policies. By all questions please contact the Odoo Apps Store representatives directly.

The easiest approach is to use the Odoo store built-in workflow:

1. Open the module's page and click the button Deploy on odoo.sh

2. After that, you will be redirected to the GitHub page. Login to your account and click 'Create a new repo' or use the existing one. Please, make sure, that your repository is private. It is not permitted to publish the apps under the OPL-1 license. If necessary, create a new repo for your Odoo.sh project

3. Then, go to odoo.sh and click on the deploy button, submit the decision in the pop-up window and click 'Continue'. The action will trigger the installation process.

These steps would install the app for your project production branch. If you wanted to deploy the apps for other branches or update the module, you should undertake the following actions:

1. Upload the source code for the app from the Odoo store

2. Commit the module to a required GitHub repository. Make sure that none of the app folders/files are ignored (included in the .gitignore of your repo). Repositories are automatically created by odoo.sh, which might add by default some crucial items there (e.g. /lib). You should upload all module directories, subdirectories, and files without exceptions

3. Deploy a target branch of the odoo.sh project or wait until it is automatically built if your settings assume that.

  1. Unzip source code of purchased tools in one of your Odoo add-ons directory

  2. Re-start the Odoo server

  3. Turn on the developer mode (technical settings)

  4. Update the apps' list (the apps' menu)

  5. Find the app and push the button 'Install'

  6. Follow the guidelines on the app's page if those exist.

Yes, sure. Take into account that Odoo automatically adds all dependencies to a cart. You should exclude previously purchased tools.

A red/orange warning itself does not influence features of the app. Regretfully, sometimes our modules do not pass standard automatic tests, since the latter assumes behavior which is in conflict with our apps goals. For example, we change price calculation, while standard Odoo module tests compare final price to standard algorithm.

So, first of all, please check deployed database features. Does everything work correctly?

If you still assume that warning influences real features, please contact us and forward full installation logs and the full lists of deployed modules (including core and third party ones).

Regretfully, we do not have a technical possibility to provide individual prices.

No, third party apps can not be used on Odoo Online.

Yes, all modules marked in dependencies are absolutely required for a correct work of our tool. Take into account that price marked on the app page already includes all necessary dependencies.  

The price for our modules is set up in euros. The Odoo store converts prices in others currencies according to its internal exchange rate. Thus, the price in US Dollars may change, when exchange rate changes.

Odoo file manager: google Drive synced

Synchronize Odoo folders with Google Drive

Odoo objects' folders in Google Drive

Document-related folder in Google Drive

Odoo attachment box synced to Google Drive

Google Drive: sync attachments

Odoo folder structure in Google Drive

Google Drive subdirectories

The root folder is in Google Drive

Odoo's root folder is in Google Drive

Odoo demonstration databases (live previews)

For this app, we might provide a free personalized demo database.

To demand such a database, press the button "Live Preview" on the top of this page or copy the link https://faotools.com/s/duk175

No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.

By your request, we will prepare an individual live preview database, where you would be able to apply any tests and check assumptions for 14 days.

Bug reporting

In case you have faced any bugs or inconsistent behavior, do not hesitate to contact us. We guarantee to provide fixes within 60 days after the purchase, while even after this period we are strongly interested to improve our tools.

To send us a bug report: press the "Website" link on the top of this page and push the button "Bug Report" (the tab Support). Alternatively, copy the link https://faotools.com/s/vzjyou

No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.

Please include in your request as many details as possible: screenshots, Odoo server logs, a full description of how to reproduce your problem, and so on. Usually, it takes a few business days to prepare a working plan for an issue (if a bug is confirmed) or provide you with guidelines on what should be done (otherwise).

Public features requests and module ideas (free development)

We are strongly motivated to improve our tools and would be grateful for any sort of feedback. In case your requirements are of public use and might be efficiently implemented, the team would include those in our to-do list.

Such a to-do list is processed on a regular basis and does not assume extra fees. Although we cannot promise deadlines and final design, it might be a good way to get desired features without investments and risks.

To share ideas: press the "Website" link on the top of this page and push the button "Share Features Ideas" (the tab Support). Alternatively, copy the link https://faotools.com/s/7gbg29

No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.

Questions and misc issues

Feel free to contact us with any other concerns, doubts, or questions: press the "Website" link on the top of this page and push the button "Raise Question" (the tab Support). Alternatively, copy the link https://faotools.com/s/qqi90v

About the team

faOtools (faotools.com, former odootools.com) is the team of developers and business analysts to help you extend Odoo's potential. We have been communicating with end users to whom the software became the main business tool since 2012. As a result, we are proud of dozens of successful Odoo apps developed. We are open for new ideas and challenges to create the best Odoo apps for business needs all over the world.

You may like the tools

KnowSystem: Knowledge Base System

The tool to build a deep and structured knowledge base for internal and external use. Knowledge System. KMS. Wiki-like revisions.

298 268
Universal Appointments and Time Reservations

The tool for time-based service management from booking appointments to sales and reviews

399 359
Password Manager

The tool to safely keep passwords in Odoo for shared use. Shared vaults

188
KPI Balanced Scorecard

The tool to set up KPI targets and control their fulfillment by periods. KPI dashboard. Dashboard designer. KPI charts

198
Cloud Storage Solutions

The tool to flexibly structure Odoo attachments in folders and synchronize directories with cloud clients: Google Drive, OneDrive/SharePoint, Nextcloud/ownCloud, and Dropbox. DMS. File Manager. Document management system

245
OneDrive / SharePoint Odoo Integration

The tool to automatically synchronize Odoo attachments with OneDrive files in both ways

394
ownCloud / Nextcloud Odoo Integration

The tool to automatically synchronize Odoo attachments with ownCloud/Nextcloud files in both ways

394 379
Dropbox Odoo Integration

The tool to automatically synchronize Odoo attachments with DropBox files in both ways

394 379
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.