If you are on Google Workspace, your CRM already talks to the Google side.
Gmail connects over OAuth; the connection covers email sending and calendar sync, not two-way inbox sync. Google Calendar works in both directions — pulling, creating, updating and deleting. The surface you will rely on in order to connect Gemini is the REST API authorised with OAuth2; we build it as a project whose scope is defined during discovery.
"We're on Google, so it reads the CRM too" — it does not
In a company that uses Google Workspace, Gemini is not a choice but an encounter: you open Gmail, it is there; you write a document, it is there. That habit produces a very reasonable assumption — “we're on Google, so it reads the CRM too.” It does not. The CRM is a separate system and the door between them has to be opened. This is the picture we see in our own implementation meetings:
- Correspondence with the customer sits in Gmail, the appointment in the calendar, the quote and the record somewhere else. All three belong to the same customer but they are not attached to the same record.
- In a purchasing meeting, “do you have a Google integration?” is asked as though it were a single question. In fact it contains five separate products: Gmail, Calendar, Drive, Docs, Meet. Saying “yes” to all five is easy; telling apart which of them is actually in place is hard.
- The AI question is asked with the same blur. The phrase “AI-powered” does not say which model looks at which data with which permission.
- IT asks something else: which data goes where, who turned it on, can it be revoked?
This page separates all four. On the Google side there are two connections that are measured and live today, there are four products that are out of scope, and for Gemini there is a path that has to be built. We do not put the three in the same sentence.
There are two things live on the Google side — and neither of them is Gemini
We have no out-of-the-box module for Gemini and we are not going to say that we do. The connection is built as an integration project using the REST API, OAuth2, webhooks and import/export, with its scope defined in the discovery call. We also have no partnership with Google, no joint programme and no approved AI pairing; because we do not have one, we do not imply one either.
Rapi, the assistant inside the product, runs on Anthropic Claude — not on Gemini. Our 18-tool MCP package, downloaded from the Setup screen, is today defined as a Claude connector; we cannot say that it has been tested with any other AI client, and because we have not tested it we do not say so. You will not find the sentence "Gemini-powered CRM" on this page.
By contrast, there are two connections that really are live on the Google side — and they are the most concrete part of this page: you connect your Gmail account over OAuth, and the connection covers email sending and calendar sync — mail you send lands on the relevant customer record, but this is not two-way inbox sync and inbox reading is switched off; Google Calendar works both ways — events are pulled, and are also created, updated and deleted from the CRM; the sync runs on a schedule. In the product, calendar sync is specific to the Google side only. The details of both are on the Google Workspace integration and email integration pages; we do not repeat them here.
We write what is out of scope with the same clarity: the product has no connection for Drive, Docs, Sheets or Meet. It would have been easy to say "with all Workspace apps"; that is not the measured situation.
When you want to connect Gemini to the CRM, the surface you will rely on is the product's open API: the product ships out of the box with 183 business objects and each one is published in the REST API with its own data and schema endpoint — you can read the field structure from outside with describe. Alongside it there are OAuth2, a composite endpoint that carries 25 sub-requests in a single request, and bulk endpoints that work on up to 200 records per call. We can say that this surface really is usable from outside on the strength of a measured fact: in one live customer installation, a third-party ERP integrator reads and writes records over this same REST API. We do not give a name because we do not have permission to publish it; this is a single installation, not a list of case studies. The same framework as it applies to an ERP is on the Netsis integration page, and our general approach is on the integrations page.
Wednesday 09:35 — the day starts in Gmail. Once the connections are in place, this is what changes:
-
1
Email you send to the customer is attached to the record
Once your Gmail account is connected over OAuth, the connection covers email sending and calendar sync: mail you send lands on the relevant customer record. This is not two-way inbox sync — inbox reading is switched off. When the rep changes, that history stays with the company.
-
2
Appointments work in both directions
Events are pulled from Google Calendar; events are also created, updated and deleted from the CRM. The sync runs on a schedule, so nobody has to copy anything by hand.
-
3
"When did we last speak?" is answered from the record
The meeting history is read from the customer record rather than by searching the calendar. Correspondence, appointment and opportunity sit side by side on the same card.
-
4
The Gemini side is opened by a separate permission decision
When the connection is built, which object gets read permission and which gets write permission is written out one by one in the scope. We do not grant access that is open to everything by default.
-
5
Every change made leaves a trace
Writes made over the API land in the field-level change history: when which field moved to which value. The audit trail also covers an assistant coming from outside.
-
6
The relationship with the provider stays in your name
You use your own Google account and your own AI subscription. The contract on that side is between you and your provider; we do not sell tokens or credits in between.
A scenario that works if you connect Gemini over the REST API: the pre-meeting briefing
-
1
Permission starts narrow: read only
The connection is built through your own Google account; which connection route is used on the Gemini side is chosen during discovery, according to what the client supports at that time. As a starting scope we recommend read-only permission on the customer, opportunity and activity objects.
-
2
The client reads the field structure itself
Which object has which fields is read from outside with the describe endpoint. You do not have to hand over a field list; a custom field added during implementation shows up at the same endpoint.
-
3
One question before the meeting, one summary back
When you ask “where do things stand with the company I'm seeing tomorrow?”, the client reads that customer record, its open opportunities and its latest activities; the composite endpoint, which carries several objects in a single request, exists for exactly this.
-
4
If writing is opened, it leaves a trace
If you want Gemini to write the meeting note, write permission is opened within the same scope. Every write made over the API lands in the field-level change history: which field, when, and to which value it moved.
The surface you rely on on the Google side
Gmail — live today
Your account connects over OAuth; the connection covers email sending and calendar sync, and mail you send lands on the relevant record. This is not two-way inbox sync — inbox reading is switched off. Generic IMAP/SMTP is not supported, and Outlook and Microsoft 365 connections are not live.
Google Calendar — two-way
Events are pulled; they are created, updated and deleted from the CRM. The sync runs on a schedule and, in the product, is specific to the Google side only.
183 business objects, each with its own endpoint
The product ships out of the box with 183 business objects and each one is published in the REST API with its own data and schema endpoint. This is the surface an AI client will rely on; the field structure is read from outside with describe.
Authorisation with OAuth2
Access is granted with OAuth2; no user password is shared. You define the scope, and you can withdraw it just as you granted it.
describe, composite and bulk endpoints
The schema is read from the API; composite carries 25 sub-requests in a single request, and bulk endpoints work on up to 200 records per call.
The change history covers writes
Writes made over the API land in the field-level change history; the field an AI touched can be seen afterwards.
What exists on the Google side, and what does not?
| Topic | Status today | How it is built |
|---|---|---|
| Gmail | Live today: connects over OAuth; the connection covers email sending and calendar sync, and mail you send lands on the relevant record — not two-way inbox sync, inbox reading is switched off | You connect your account over OAuth; the details are on the email integration page |
| Google Calendar | Live today and two-way: pull, create, update and delete; runs on a schedule | Set up with the Google account connection; in the product, calendar sync is specific to Google |
| Gemini | We do not have a Gemini connection built into the product | Built over the REST API and OAuth2, as a separate piece of work whose scope is defined during discovery |
| MCP package — 18 tools | Today it is defined as a Claude connector | We cannot say that it has been tested with Gemini; and because we have not tested it, we do not say so |
| Drive, Docs, Sheets and Meet | Out of scope; we have no code that connects to these products | We do not offer it. Attachments and files are kept in the CRM's own file storage |
| App verification on the Google side | We share its status in writing before implementation | That is why there is no sentence such as "it connects without a hitch" on this page |
What we have verified
How is the Google side brought into service?
-
1
Discovery
We work out who administers your Workspace tenant, who the Gmail and Calendar sync will cover, and how you use Gemini today. We recommend that your IT lead is in this meeting.
-
2
Scope and permission table
Which user's account will be connected, and which object gets read permission and which gets write permission, are written down. The Workspace products that stay out of scope are also listed explicitly in the same document.
-
3
Configuration and a limited start
The Gmail and Calendar connection is set up over OAuth and verified with sample records. The AI side is opened with a narrow scope; we recommend limiting the initial scope to read only, with write permission extended later and by your decision.
-
4
Training and go-live
The team is shown what the sync does and how the change history is read. We do not commit to a duration before discovery; after the discovery call we give you a date, not a range. The scope of the project-specific connection is also settled in that same discovery.
Our limits: what we do not promise on this page
Under the Google heading, the thing that is easily overstated is scope; under the AI heading, it is the implication of a partnership. We write down what we do not promise, by name.
- We do not say “Gemini-powered CRM”. Rapi, the assistant inside the product, runs on Anthropic Claude.
- We have no partnership with Google and no approved AI pairing and we do not imply such a relationship.
- We do not say that our MCP package works with Gemini. The package is today defined as a Claude connector and we have not tested it with any other client. If you want to connect another assistant, the path is the REST API and OAuth2; that is a separate piece of work whose scope is defined during discovery.
- We do not say “it works with all Workspace apps”. Drive, Docs, Sheets and Meet are out of scope; we have no code that connects to these products.
- We do not say “it connects without a hitch”. We share our app verification status on the Google side in writing before implementation; we do not leave what you will see on the connection screen as a surprise.
- We do not sell autonomous agents. In the product's own assistant, the number of steps that can be taken in a single request is limited — eight at most.
- We do not promise that your stock will be in sync, that the order → invoice → collection chain will flow by itself, or production/MRP automation. We have written the reason for all three, and what can be done instead, in one place: the three things we do not promise.
AI and consent: the product's own assistant is off by default; unless you turn it on, your CRM data is not sent to any AI provider. When you connect your own Gemini client, you are the one who has made that decision, and we define its scope in writing during implementation: which object, which permission, which user. Seen from Türkiye this is a transfer abroad and falls within the scope of Article 9 of Law No. 6698; we establish its legal basis together during the contract process. Our sub-processor list is on our security page.
Data location: your data is kept in the European Union — the database in Helsinki (Finland), files in Frankfurt, backups in Falkenstein (Germany). We have no component in Türkiye and we have no such feature as region selection. With the Gmail and Calendar connection, your mailbox and your calendar continue to stay on the Google side. The details are on the security page and in the KVKK privacy notice.
Certification: we do not have an ISO 27001 or SOC 2 certificate, and we will not claim one until we do. We fill in your enterprise security assessment questionnaires and describe the architecture in writing.
We keep plan prices in one place, out in the open
The scope of the connection on the Google side, and its cost if there is one, are worked out in the discovery call and shared in writing. Plan prices and separately priced items we publish on a single page, with the figures.
Three plans, the scope table and separately priced items, all on one page.
Frequently asked questions about the Gemini integration
Can we connect Gemini to Rapitek CRM?
Is Rapitek CRM a "Gemini-powered" CRM?
Do you have a partnership with Google?
Does your MCP package work with Gemini as well?
What is live on the Google Workspace side today?
Is the Google Calendar sync really two-way?
Do Drive, Docs, Sheets and Meet connect?
If our Gmail correspondence lands in the CRM, can Gemini read it too?
Will we run into a verification screen when we connect our Google account?
If the connection is built, can Gemini write records to the CRM?
Does our CRM data go to Google?
Is the AI assistant on by default?
How long does implementation take, and is it included in the plan price?
Where is our data kept?
Can we see it before buying?
Let's make the Google side clear in 30 minutes
In the demo, let us show how the Gmail sync lands on the record and how Google Calendar works in both directions; and let us talk through together what has and has not been measured on the AI side.
The Workspace products that stay out of scope are also listed explicitly in the written scope.
