| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Calendar (calendar)
• Discuss (mail) |
| Lines of code | 954 |
| Technical Name |
gb_google_microsoft_calendar_two_way_sync |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Calendar (calendar)
• Discuss (mail) |
| Lines of code | 954 |
| Technical Name |
gb_google_microsoft_calendar_two_way_sync |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Google / Microsoft Calend
Two-way calendar sync to Google Calendar and Microsoft 365 using your own OAuth app (BYOK)
Calendar drift between Odoo and your team's Google or Microsoft 365 calendars causes missed meetings and double-bookings. This Bring-Your-Own-Keys connector registers your own Google or Microsoft OAuth client, connects each user's calendar with the standard authorization-code + refresh-token flow, and synchronises events both ways. Outbound, Odoo calendar.event create/update/cancel is pushed to the remote calendar; inbound, remote events are pulled with a delta/sync token and mirrored back — with a stable mapping table so the two directions never loop. The network calls use your credentials; nothing routes through us.
Key Features
BYOK OAuth Accounts
Register a Google or Microsoft OAuth client (client id / secret) and connect each user's calendar; tokens are stored per account and refreshed automatically when they expire.
Outbound Sync
Odoo event create / update / cancel is pushed to the linked remote calendar — mapping title, description, location, start/stop, all-day and attendees — storing the remote event id for idempotent updates.
Inbound Delta Sync
Remote changes are pulled via Google syncToken or Microsoft Graph delta links and mirrored into Odoo — creating, updating or cancelling the matching event efficiently.
Loop-Proof Mapping
A mapping table links each Odoo event to its remote counterpart per provider, with a content hash so unchanged events are skipped and the directions never ping-pong.
Conflict Policies
Choose "last writer wins" or "Odoo wins" to resolve simultaneous edits deterministically, applied per mapping.
Robust Transport & Logging
A thin REST client builds Google Calendar v3 and Microsoft Graph payloads, refreshes tokens on 401, paginates and surfaces clear errors. A cron runs the sync; per-account on-demand sync and a full sync log are included.
Your Credentials, Your Data
BYOK means events flow directly between your Odoo and your Google/Microsoft tenant — no third-party relay, no vendor lock-in.
Genuinely Two-Way
Full mapping, payload-building and reconciliation logic on both providers — not a one-direction export.
Screenshots
Calendar Accounts
Sync Log
Event Mappings
Why Choose This Module
Teams living in Google Workspace or Microsoft 365 who also schedule in Odoo, sales and services organisations needing reliable calendar alignment, and IT admins who want OAuth credentials and data to stay under their own control.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: LGPL-3
- Languages: 35+
- Author: Baris Genc
- Dependencies: base, calendar, mail
- Support: odoo@gencbaris.com
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