Google Drive Odoo Integration v.14

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

394€

The price already includes all necessary dependencies = 149€ (own price) + 245€ (Cloud Storage Solutions) .
Current version: 14.0.1.0.2

Enterprise
Community
Odoo.sh

This is the tool to integrate Google Drive features into your Odoo business work flow. The app automatically stores Odoo attachments in Google Drive, and it provides an instant access to them via web links. In such a way users work with files comfortably in the cloud storage, while the results are fully available in Odoo.

Automatic regular sync

Synchronization between Odoo and Google Drive is based on scheduled jobs. No manual interaction is required

Bilateral Google Drive 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

Any Odoo document types for sync

Decide which Odoo document types should be synced. Customers, opportunities, sale or purchase orders, tasks or issues, employees or users, etc. Custom models are also supported

Instant access for Google Drive

The tool redefines Odoo attachments boxes to make work comfortable: download files locally without login, open files and folders in Google Drive (if possible, items would be opened in Google Drive editors and previewers), use standard Odoo previewers

Compatible with Odoo Enterprise documents

Reflect Odoo Enterprise Documents' structure and items in Google Drive. All features (including sharing, downloading, and signing) would anyway work

Google team and individual drives

Sync works both for individual and team drives (Google Suite business and enterprise tariffs). In the latter case the root folder Odoo is placed within a chosen team drive, in the former case - within a current user drive

Google Drive sync history

Sync activities might be logged. Control over files and folders creations, moves, name changes and removals. Just turn on the option 'Log sync activities', and you would be able to observe the history through the button 'Sync logs'

Default folders

The tool let generate default directories' structure for this document type during the very first sync of a related object. For example, for all employees you may have pre-defined folders 'Scans', 'Scans/Official', 'Photos', etc.

Integrate Odoo and Google Drive
Odoo attachments as Google Drive files

Excellent !!!

Great App and great Service from faOtools.

Carlos A. Villarreal C. in the Odoo Apps Store

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 in the Odoo Apps Store

Sync any documents you like

Configuring models to sync

  • To sync a specific document type, you should add it as a model to sync. Any Odoo model might be chosen
  • The app let split models into a few folders based on selected filters. Use any document storable field to distinguish a directory. Have a separate folder for individuals and companies, for European and American opportunities, for quotations and confirmed orders, for each project, etc.
  • Limit also documents by relative periods through using date fields of linked documents. For example, leads registered in the last 3 months or invoices updated the last week
  • Define name expressions to specify titles of documents' Google Drive folders. For instance, to include project name to a task directory
  • Prepare hierarchy of default folders to be created when a document directory is synced to Google Drive for the first time

Typical use cases

  • Projects: have an own Google Drive folder for each customer project
  • Customers: add all partner files in a single directory available both from Odoo and from Google Drive. Modify those using default cloud editors and access them when working in Odoo
  • Employees: gather all files by this employee in a single cloud folder: photos, document scans, contracts. Access and upload those from Odoo and Google Drive alternatively
  • Opportunities: carefully store all specifications, requirements, any files which would let you make a good offer
  • Orders: keep all printings and contracts in Google Drive with instant availability from Odoo
  • Picking operations: save warehouse docs to Google Drive.
Google Drive documents filtered
Any Odoo model to be synced

How synchronization works

Direct Sync

  • Direct synchronization is based on the scheduled job 'Synchronize attachments with cloud'
  • Direct sync make all synced Odoo attachments change their type to a link (URL), while binary content is removed with a next Odoo cleaner. So, no actual files would be stored on your Odoo server
  • Direct sync checks whether attachments are added or deleted for synced documents. If so, they would be created or removed in Google Drive
  • Direct sync checks whether a new document type (e.g. sale orders) is added / renamed / replaced in the to-sync-models configurations. If so, this should be reflected in Google Drive
  • Direct sync checks whether a new document (e.g. quotation SO-001) related to a synced document type is generated / updated / unlinked. If so, the connector would make the same changes in Google Drive
  • The final goal of direct Google Drive integration is to have the structure 'Odoo / Document Types / Documents / Files. For example, 'Odoo / Quotations / SO019 / commercial offer.pdf'

Backward Sync

  • Backward synchronization is based on the scheduled job 'Synchronize attachments from cloud'
  • Backward sync checks whether any items are added to a Google Drive document folder. If so, the app would create URL attachments for that items in a linked Odoo object
  • Backward sync checks whether any items are deleted / moved in a cloud document folder. If so, a linked Odoo attachment would be also unlinked or moved
  • Backward sync checks whether any item is renamed in Google Drive. If so, a chained Odoo attachment should be also renamed
  • In Google folders you can put not only files but also child folders. In that case a link for this folder (not its content) would be kept in Odoo attachments
  • If you deleted a folder related to this document type or this document, their child files would be deleted as well. Thus, Odoo would remove related attachments. The folders, however, will be recovered with a next direct sync

Misc notes

  • The connector works on a queue (first in - first out) principle: it tries to firstly reflect the oldest changes
  • Each sync, especially the very first one, might take quite a long. It is not recommended to make sync too frequent: once an hour seems reasonable frequency
  • File names and content should be managed in Google Drive: each backward sync would recover Google Drive names, Odoo is here less important
  • Take into account that files or folders deleted in Google Drive are really deleted only when you clean trash. Otherwise, such files still exist and would be reflected in Odoo
  • Try to avoid the following symbols in folders' and files' names: *, ?, ", ', :, <, >, /, +, %, !, @, \, /,. Direct sync will replace such symbols with '-'. It is done to avoid conflicts with file systems.

Odoo Enterprise Documents

  • The special add-on 'Cloud Sync for Enterprise documents' is introduced to synchronize Google Drive with the Odoo app 'Documents' (the latter is distributed under the Odoo Enterprise license)
  • Based on that add-on the Odoo documents' hierarchy would be reflected within the folder 'Odoo / Odoo Docs'
  • Each Odoo folder would have a linked Google Drive folder. Take into account that folders created in the cloud storage will be synced as Odoo attachments. The key principle is: folders are managed by Odoo, files are managed by the cloud client
  • All files are synced with the same logic as usual attachments. Files created in Odoo will be added to the cloud storage and will be replaced with links in Odoo. Files created in cloud storage will generate URL attachments within a paired documents directory
  • Standard Google Drive sync and integration with Enterprise Documents are done within the same jobs. Avoid the scenarios when a single file is synced as a simple Odoo attachment and as an Odoo document simultaneously
  • Odoo spread sheet files are not synced by the connector: so, they are still manageable in Odoo
  • Please do not name synced models as 'Odoo Docs'. This is the reserved name for Odoo Enterprise Documents.
Odoo documents sync interface
Direct link to Google Drive

Configuration and Installation Tips for Google Drive Odoo Integration Odoo v.14

Login and Google Drive Credentials

  1. Go to the Google Developer Console via the url https://console.developers.google.com
  2. Select or create a project
  3. Find the section 'Dashboard' and press 'ENABLE APIS AND SERVICES'
  4. Find Google Drive API and push the button to enable its API
  5. Go to 'Credentials' and press the button 'Configure Consent Screen'. As the User Type select 'External' and push 'Create'
  6. 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'
  7. On the 'Scopes' page just press 'Save and Continue'
  8. As Test Users add your GMail email address, then press 'Save and Continue'
  9. 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'
  10. Go to the Odoo Google Drive Settings
    • Copy 'Client ID' to the 'App Client ID'
    • Copy 'Client Secret' into the field 'App Secret Key'
    • Insert previously generated redirect url
    • If you use team drives, check the related box. Make sure you really use team drives. In you 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 for this team drive
  11. Press 'Save'
  12. Press 'Login and Confirm'. Odoo redirects you to Google login page. Check in, agree with all conditions, and grant permissions asked
  13. After login, Google redirects you back to Odoo. Google Drive - Odoo synchronization is ready to be done.

Google Console: APIs

Google Console: APIs

Google Drive API

Google Drive API

Enable Google Drive API

Enable Google Drive API

Configuring Google Consent Screen

Configuring Google Consent Screen

Setting up External User Type API

Setting up External User Type API

Entering Google app details

Entering Google app details

Google app scopes

Google app scopes

Adding authorized users

Adding authorized users

Creating Google app credentials

Creating Google app credentials

Google Drive app redirect URL

Google Drive app redirect URL

Copy app credentials

Copy app credentials

Enter Google app credentials to Odoo

Enter Google app credentials to Odoo

Odoo server configuration and cron job configuration

To make sure the synchronization works correctly apply proper timeouts to the Odoo configuration file: LIMIT_TIME_CPU, LIMIT_TIME_REAL, LIMIT_TIME_REAL_CRON should be more than 900 seconds.

For Odoo.sh this should not be done, since timeouts are predefined and are not configurable.

Then, timeout should be entered to your Odoo. To that goal find the section 'Settings' on the app configuration page and copy the number there.

Afterwards, it is needed to make the cron jobs suit the applied timeouts. In the debug mode go to the Settings > Technical > Automation > Scheduled Jobs:

  • Set up the job 'Synchronize attachments with cloud' as (a) frequency - 2*timeout; (b) the next execution as the next hour +timeout. For example, for 900seconds timeout: frequency - as 30minutes; the next execution - at 08:15
  • Set up the job 'Synchronize attachments from cloud' as (a) frequency - 2*timeout; (b) the next execution as the next hour + timeout*2. For example, for 900seconds timeout: frequency - as 30minutes; the next execution- at 08:30.

Frequently Asked Questions about Google Drive Odoo Integration Odoo v.14

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.

Yes, you can. To this end:

  1. Turn on debug mode

  2. Go to technical settings > Automation > Scheduled jobs

  3. Find the jobs 'Synchronize attachments with cloud' and 'Update attachments from cloud'.

Take into account that you should not make them too frequent. It is preferable this job is finished until a new one is started. Thus, the configuration should depend on how many items you to sync you have. Usually, the frequency is set up between 15 minutes to 4 hours.

Make also sure that you have set up enough time limits in your Odoo configuration file. Thus, LIMIT_TIME_CPU and LIMIT_TIME_REAL parameters should be equal or bigger than planned cron job time. Starting from the version 13 consider also the parameter LIMIT_TIME_REAL_CRON.

An import notice for Odoo.sh clients: the maximum time for cron job might be set up as 15 minutes only.

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, this feature is available only from version 15. Prior to that version, the module works with the pre-defined structure of folders:

  1. Odoo - a core folder for sync

  2. Models - folders for each Odoo document type. For example, 'Projects', 'Partners'. Distinguished by domain there might be more specific folders: e.g., 'Customer 1 Projects', 'Projects of the Customer 2', 'Internal Projects', etc.

  3. Objects - folders for each document, e.g. 'Project 1' or 'Customer 1'

  4. Files and folders related to this Odoo document to be synced.

As a result you may have for instance:

  • Odoo / Projects / Project 1 / files and folders related to the  project 1

  • Odoo / Customer 1 Projects / Project 1; Odoo / Customer 2 Projects / Project 3, ...

  • Odoo / Customers / Customer 1 / files and folders related to the customer 1

This structure is always flat, meaning that there are only those levels of hierarchy. Thus, it is correct that various document types can't be done within the same structure. Within the folder 'Customer 1' we can't keep the files related both to sale orders, invoices, and projects. Each of those document type has an own (or a few own) folders. Otherwise, we will not have a chance to make backward synchronization, since there would be no criteria to rely upon.

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 a 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.).

No, the tool relies upon a single user end point. It means that all sync processes are done under a single cloud admin (app). Access rights for created folders / files are not automatized. You should administrate those rights in your cloud storage solution.

No, the tool is only a technical core. You also need the connector for your cloud client.

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.

For models' directories (sale orders, opportunities, suppliers, etc.): you may assign your own name for any document type.

For objects' folders (SO-001, John Smith, etc.): the tool relies upon the Odoo 'name_get' method for this document type. However, you can change that by defining name_expression. The same syntax as for Odoo email templates is used. 

No, this feature becomes available only from version 15.

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.

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.  

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).

Odoo demonstration databases (live previews)

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

No phone number or credit card are 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 to check assumptions during 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 during 60 days after a purchase, while even after this period we are strongly interested to improve our tools.

No phone number or credit card are 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: screen shots, Odoo server logs, full description of how to re-produce your problem, and so on. Usually it takes a few business days to prepare a working plan by an issue (if a bug is confirmed) or provide you with guidelines what should be done (otherwise).

Public features request 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 into our to-do list.

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

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

New features and extra Odoo services (individual development)

Each of our apps might be customized and extended to suit your specific requirements.

Our customization team fulfills not only such jobs but it also provides a full range of Odoo services. From simple modifications and consultations to complex enterprise projects. The team has completed over 100 implementations since 2012, and might help with any technical or business needs.

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

You may also like the tools
Cloud Storage Solutions

The technical core to synchronize your cloud storage solution with Odoo

245€
OwnCloud / NextCloud Odoo Integration

The tool to automatically synchronize Odoo attachments with OwnCloud / NextCloud files in both ways

394€
OneDrive / SharePoint Odoo Integration

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

394€
DropBox Odoo Integration

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

394€
KnowSystem: Knowledge Base System

The tool to build deep and structured knowledge base for internal and external use. Knowledge System. KMS

298€
Universal Appointments and Time Reservations

The tool for time-based service management from booking appointment to sale and reviews

399€
KPI Balanced Scorecard

The tool to set up KPI targets and control their fulfillment by periods

198€