Gmail
Mail sent from Odoo through your Google account using OAuth, and replies logged against the lead, customer or ticket they belong to.
Your team already lives in Gmail, Calendar and Drive. The point of connecting Workspace to Odoo is not to move them out of those tools, which never works, but to stop the ERP being a separate island they have to remember to update.
Done well, an email about a deal is on the deal, a site visit is on both calendars, and the signed contract is linked to the customer rather than sitting in someone’s personal Drive.
Businesses running Odoo with OdooBots
Odoo Google Workspace integration ties Gmail, Calendar, Drive, Contacts and Meet to the Odoo records they relate to, with Google as the sign-in. Emails are logged on the lead or customer, meetings sync both ways between Calendar and Odoo, Drive and Docs files are linked to the record rather than copied, contacts stay aligned, Meet links are generated on the meeting, and users sign in with their Google account over OAuth instead of a second password.
Documents are linked, not duplicated. A Google Doc stays in Drive with its sharing and version history intact, and Odoo holds the reference — copying files into the ERP creates two versions and nobody knows which is current.
Six parts of Workspace connect to Odoo, and most of the value is in where a record ends up rather than in the sync itself.
Mail sent from Odoo through your Google account using OAuth, and replies logged against the lead, customer or ticket they belong to.
Two-way synchronisation of meetings and activities, so a site visit created in either place appears in the other with its attendees.
Drive files and folders linked to the Odoo record — quotation, project, customer — keeping Drive sharing and version history as they are.
A document or spreadsheet attached to the record it supports, so the proposal being edited is the one the opportunity points at.
Google Contacts aligned with Odoo contacts, with matching rules so one person does not exist three times across both systems.
Meet links generated on a scheduled meeting, and users signing into Odoo with their Google account rather than a separate password.
A salesperson emails a prospect from Odoo; it leaves through Gmail using OAuth, and the reply lands back on the opportunity. They book a demo, which appears in their own Google Calendar with a Meet link and on the Odoo activity list. The proposal is a Google Doc, linked to the opportunity rather than copied into it, so the version everyone opens is the one being edited.
Mail sent through OAuth rather than a stored password
Calendar synced both ways, with a rule for who wins on a clash
Drive and Docs linked to records, never copied into them
Contacts matched before creating, so people are not duplicated
Google sign-in set up at the domain level, not per person
These are the decisions that are cheap to make now and painful to reverse once two systems have been exchanging records for a month.
Domain-level approval so the integration works for everyone. Without it each user configures their own connection and half of them never do.
Which side wins when the same meeting is changed in both. Needed before two-way sync is switched on, not after.
Which emails attach to a lead or customer, and which stay private. Logging everything is rarely what the team expects.
Where documents for a customer or project live, and who can see them, agreed before files start being linked.
How a Google contact is paired with an Odoo contact, including shared addresses and personal entries that should not sync at all.
Whether Google becomes the only way into Odoo, and what happens for users without a Workspace account.
What happens to synced calendars, linked files and logged mail when someone leaves. Rarely asked, always needed eventually.
We would rather say this before you buy licences than after. These are the areas where we scope real development, recommend a different tool, or tell you the connector will not reach.
Editing happens in Google. Odoo holds the link and the context, which is the right division of labour.
Logging every email into the ERP is possible and almost never wanted. Selective logging on records is the useful version.
Drive sharing rules stay in Google. Odoo record access and Drive access are two different permission systems.
Live two-way sync with a spreadsheet is fragile by nature. Where it is genuinely needed, it is scoped as custom work.
Working with Odoo records from inside Gmail depends on the add-on and its own limits, which differ from the core integration.
Consumer Gmail accounts behave differently from Workspace. Domain-level features need a real Workspace tenant.
Connecting Google Workspace to Odoo is less about the connector than about agreeing what is true where, and what happens when a record will not go through.
Understand which Workspace apps your team actually uses, whether you have admin access to the domain, and what should be logged against records.
Agree admin consent, the calendar conflict rule, what gets logged, the Drive structure and the sign-in policy before anything is connected.
Connect Google Workspace to Odoo using the standard connector where one fits, and build only what the connector genuinely cannot reach. See Odoo customization.
Your records, in a test database, including the awkward ones — the cancelled order, the partial refund, the product that exists on one side only.
A queue for failed records with a named owner and an alert, because an integration nobody watches diverges quietly and the divergence is found at audit.
Cutover with a reconciliation on both sides, then hypercare, then ongoing support and AMC.
We do not publish one integration price, because the same connector costs very differently depending on the factors below. We do publish what moves the number, and the price is fixed in writing before work starts.
We link Google documents to Odoo records rather than copying them in, because two copies of a proposal is worse than none. And we start with domain admin consent, since that is what makes the integration work for the whole team instead of for the one person who set it up.
Product capabilities stated on this page are documented by Odoo. The mapping advice, failure handling and limitations come from our own integrations.
Tell us whether you have Workspace domain admin access and which apps your team really uses. Those two answers decide the rollout, and the diagnosis call is free.