If you are on Google Workspace, your CRM already talks to the Google side.
Gmail connects with your Google permission; the connection covers email sending and calendar sync, not two-way inbox sync. Google Calendar works in both directions: pulling, creating, updating and deleting. Our AI connector, in turn, is designed to connect to Gemini CLI and Gemini Enterprise through the open MCP standard; we set it up together with you.
"We're on Google, so it reads the CRM too": that takes a connection
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 answers all four: the two connections that are live today on the Google side, how Gemini connects to the CRM through the connector, and where the data goes.
How does Gemini connect to the CRM, and what is live on the Google side today?
Rapitek CRM's AI connector works with Claude. It is in live use on claude.ai and on iOS, and you sign in with your own CRM account. Because the connector is built to the open MCP standard, it is also designed to connect to Gemini CLI and Gemini Enterprise through the “other client” route. Your administrator chooses which client families may connect on the Setup › AI Connectors screen; for these clients, we set up the connection together with you.
Rapi, the assistant inside the product, runs on Anthropic Claude. You connect Gemini to the CRM with your own account, through the connector.
On the Google side, two connections are live today: you connect your Gmail account with your Google permission, 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.
Drive, Docs, Sheets and Meet are outside these two connections; attachments and files are kept in the CRM's own file storage.
If you want to build your own integration, the product's open API is also live today: every record in the CRM, from lead to quote, from invoice to task, can be read and written through the REST API, and you can read the field structure from outside. Access is granted with permissions, without sharing passwords; up to 25 operations can be sent in a single request, and bulk transfers handle up to 200 records per request. This surface is usable from outside: ERP integrators can read and write records through this same REST API. 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, 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
Changes to existing records leave a trace
Changes made over the API to existing records land in the field-level change history: when which field moved to which value (for protected fields, only a marker). A newly created record's initial values are not recorded there. 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 once Gemini is connected: the pre-meeting briefing
-
1
Permission starts narrow: read only
The AI connector is added to Gemini CLI or Gemini Enterprise; we set it up together with you. 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 record type has which fields is read from outside through the API. You do not have to hand over a field list; a custom field added during implementation shows up there too.
-
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.
-
4
If write permission is granted, changes leave a trace
If you want Gemini to write the meeting note, write permission is opened within the same scope. Every API change to an existing record lands in the field-level history: which field, when, to which value (for protected fields, only a marker); a new note's initial values are not recorded there.
The surface you rely on on the Google side
Gmail: live today
Your account connects with your Google permission; 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.
Every CRM record within reach
From lead to quote, from invoice to task, every record in the CRM can be read and written through the REST API. This is the surface an AI client will rely on; the field structure is read from outside.
Access without sharing passwords
Access is granted with permissions; no user password is shared. You define the scope, and you can withdraw it just as you granted it.
Several operations in one request
The field structure is read from the API; up to 25 operations can be sent in a single request, and bulk transfers handle up to 200 records per request.
The change history covers changes made over the API
Changes made over the API to existing records land in the field-level change history; the field an AI changed on an existing record can be seen afterwards. A newly created record's initial values are not recorded in that history; the creator (the user the API client is bound to) and creation time are set by the system and cannot be changed from the user screens, data import or the API.
How do the Google and Gemini sides connect?
| 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 with your Google permission; 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 CLI and Gemini Enterprise | The AI connector is designed to connect through the open MCP standard, via the “other client” route | We set it up together with you |
| Claude (claude.ai and iOS) | The connector works with Claude; you sign in with your own CRM account | Your administrator enables it on the Setup › AI Connectors screen |
| Gemini app (consumer version) | Not within the scope of this connection | The app only works in the US and with a personal account |
| Drive, Docs, Sheets and Meet | Not within the scope of the Gmail and Calendar connection | 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 | We make the connection together during implementation |
The connection at a glance
How is the Google side brought into service?
-
1
Discovery
We work out who administers your Workspace account, 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 with your Google permission 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.
Scope and setup terms
What the Gemini and Google connections cover:
- Rapi, the assistant inside the product, runs on Anthropic Claude. You connect Gemini with your own account, through the AI connector.
- Google connections use Google's standard permission screen. Access is granted with permissions, without sharing passwords. This is an authorisation route anyone can use, not a business partnership or an approved pairing.
- Gemini CLI and Gemini Enterprise connect through the connector. Gemini's consumer app is not within this scope; that app only works in the US and with a personal account.
- The Workspace scope is Gmail and Google Calendar. Drive, Docs, Sheets and Meet are not connected.
- Google app verification status is shared in writing. We share our app verification status on the Google side in writing before implementation, so the connection screen holds no surprises.
- Rapi works on request, step by step. In the product's own assistant, a single request can take at most eight steps.
- Stock sync, a self-running order → invoice → collection chain and production/MRP automation are outside the scope. The reasons, and what can be done instead, are in one place: scope and setup terms.
AI and consent: the product's own AI features (the Rapi assistant, business card scanning, meeting analysis, the WhatsApp/Instagram assistant and the AI step in flows) send the relevant content to Anthropic (Claude) only when you use them or enable them in an automation. Audio recordings are transcribed on our own servers and are not sent to the AI provider. With a single switch under Setup › System Controls you can turn off all AI features, and you can turn off meeting analysis separately. 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?
Which clients can your AI connector connect to?
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?
When do the AI features send my CRM data to an AI provider?
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 intro call, let us show how the Gmail sync lands on the record and how Google Calendar works in both directions; and let us talk about which AI client you use and set up the connection together. Then we open your 7-day trial account; no credit card required.
