Google Drive Odoo Integration
by faOtools
| Technical name | google_drive_odoo |
| License | LGPL-3 |
| Website | https://faotools.com/apps/17.0/google-drive-odoo-integration-837 |
| Included Dependencies | Cloud Storage Solutions |
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.
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.
Excellent !!!
Great App and great Service from faOtools.
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.
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.
- Turn on the option 'Google Drive Sync' (cloud Storage > Configuration > Configuration). The optional add-on Google Drive Odoo Integration is required
- Go to the Google Developer Console via the URL https://console.developers.google.com
- Select or create a project
- Find the section 'Dashboard' and press 'ENABLE APIS AND SERVICES'
- Find Google Drive API and push the button to enable its API
- Go to 'Credentials' and press the button 'Configure Consent Screen'. As the User Type select 'External' and push 'Create'
- 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
- On the 'Scopes' page just press 'Save and Continue'
- As Test Users add your GMail email address, then press 'Save and Continue'
- 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'
- Publish the app on the OAuth consent screen. Otherwise, the token will be expired every week
- 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)
- Press 'Confirm'. Odoo redirects you to the Google login page. Check in the system, agree with all conditions, and grant all permissions asked
- After login, Google redirects you back to Odoo. Google Drive - Odoo synchronization is ready to be done
- Apply the newly created cloud client to folder rules and/or manual folders which should be synced to that Google Drive
- Await the sync scheduled job to be started. For testing purposes only: trigger integration manually from Cloud Storage > Configuration > Configuration > the button 'Launch sync'.
Watch also the configuration video
Google Console: APIs
Find the Google Drive API
Enable Google Drive API
Configure the Google Consent Screen
Set the External User Type API up
Enter Google app details
Define Google app scopes
Add authorized users
Registering Google app credentials
Introduce a Google Drive app redirect URL
Publish the app to avoid too frequent token expiration
Copy the app credentials
Enter Google app credentials to 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, depending on your cloud client configuration.
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:
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.
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 version 12.0 and prior gives you access to all versions up to 12.0.
- starting from version 13.0, every module version should be purchased separately.
- disregarding the version, purchasing a tool grants you a right to all updates and bug fixes within a major version.
Take into account that the faOtools team does not control those policies. For 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.
Unzip the source code of the purchased tools in one of your Odoo add-ons' directories;
Re-start the Odoo server;
Turn on the developer mode (technical settings);
Update the apps' list (the apps' menu);
Find the app and push the button 'Install';
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).
No, we distribute the tools only through the official Odoo apps store
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
Odoo objects' folders in Google Drive
Odoo attachment box synced to Google Drive
Odoo folder structure in Google Drive
The 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/sjol38
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/hwj2w9
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/c4wt17
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/42ivqj
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
The tool to build a deep and structured knowledge base for internal and external use. Knowledge System. KMS. Wiki-like revisions.
The tool for time-based service management from booking appointments to sales and reviews
398
The tool to set up KPI targets and control their fulfillment by periods. KPI dashboards. Dashboard designer. KPI charts
198
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
The tool to automatically synchronize Odoo attachments with OneDrive files in both ways
394
The tool to automatically synchronize Odoo attachments with ownCloud/Nextcloud files in both ways
394
The tool to automatically synchronize Odoo attachments with DropBox files in both ways
394
The tool to change attachment titles on upload and auto-assign codes for files
49
This is an unofficial translation of the GNU Lesser General Public License into Vietnamese. It was not published by the Free Software Foundation,
and does not legally state the distribution terms for software that uses the GNU LGPL - only the original English text of the GNU LGPL does
that. However, we hope that this translation will help language speakers understand the GNU LGPL better.
GNU LESSER GENERAL PUBLIC LICENSE
Version 3, 29 June
2007
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License,
supplemented by the additional permissions listed below.
0. Additional Definitions.
As used herein,"this License" refers to version 3 of the GNU Lesser General Public License, and the "GNU GPL" refers to version 3 of
the GNU "General" Public License.
"The Library" refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
An "Application" is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library.
Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library.
A "Combined Work" is a work produced by combining or linking an Application with the Library. The particular version of the Library
with which the Combined Work was made is also called the "Linked Version".
The "Minimal Corresponding Source" for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code
for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
The "Corresponding Application Code" for a Combined Work means the object code and/or source code for the Application, including any data
and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
1. Exception to Section 3 of the GNU GPL.
You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.
2. Conveying Modified Versions.
If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that
uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version:
a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still
operates, and performs whatever part of its purpose remains meaningful, or
b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
3. Object Code Incorporating Material from Library Header Files.
The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such
object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure
layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following:
a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License.
b) Accompany the object code with a copy of the GNU GPL and this license document.
4. Combined Works.
You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the
Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License.
b) Accompany the Combined Work with a copy of the GNU GPL and this license document.
c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices,
as well as a reference directing the user to the copies of the GNU GPL and this license document.
d) Do one of the following:
0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and
under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified
Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.
1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the
Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library
that is interface-compatible with the Linked Version.
e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the
GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by
recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information
must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation
Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.)
5. Combined Libraries.
You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that
are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of
the following:
a)Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities,
conveyed under the terms of this License.
b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying
uncombined form of the same work.
6. Revised Versions of the GNU Lesser General Public License.
The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new
versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered
version of the GNU Lesser General Public License "or any later version" applies to it, you have the option of following the terms and
conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you
received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.