If you use Claude, your CRM talks to Claude.
This connection runs in production today; setting it up does not require a provider-specific project. Rapi, the assistant inside the product, runs on Anthropic Claude and does not only read the CRM: it writes records too. You can connect your own Claude to the same CRM too: add the Rapitek connector in Claude and sign in with your own CRM account.
Why does AI end up bolted on in a CRM?
When AI comes up, two separate expectations get sold with the same sentence on the CRM side. The first is an assistant embedded in the product: one that finds what you ask for, summarises, writes. The second is the assistant the team already uses: a team that works with Claude all day wants to reach the CRM from that same window.
In both cases the mechanism jams at the same point (as we have seen it in our own projects):
- If the assistant only reads, the work is not finished: you read the summary and still open the record yourself, still fill the field in by hand.
- If the assistant is outside the CRM, copy-paste creeps in between; where the record came from is lost, and no trace is left behind.
- When AI is positioned as an add-on, the tool the team actually uses and the tool inside the CRM stay two separate worlds.
- And this question goes unanswered: where does this assistant take the data, who turned it on, can I turn it off when I want to?
This page's job is to answer those four questions one by one: first what it is, then where it stands, then where it does not.
This connection is live today, and it is really two separate things
1. The assistant inside the product: Rapi. Rapi runs on Anthropic Claude and does not only read the CRM: it writes records too. It fetches, creates and updates core records such as leads, contacts, companies and opportunities. Every field it changes on existing records lands in the product's field-level change history; the initial values of a record it creates are not recorded there.
2. Your own Claude: the MCP connector. Your administrator turns on Claude in Setup › AI Connectors; you add the Rapitek connector in Claude and sign in with your own CRM account. Within your permissions, Claude reads and writes your records and sends messages with your approval. The surface this connection rests on is the same one integrators use: a REST API where access is granted with permissions rather than shared passwords, the field structure can be read from outside, several operations can be sent in one request, and records can be transferred in bulk.
We wrote up our general approach to integrations with the same openness on the integrations page.
Wednesday 11:15, a quote is being prepared. With Rapi turned on, this is what changes:
-
1
You ask for the customer by name, and Rapi brings up the record
Company, contact and open opportunity records arrive without searching the list screen. Rapi produces the answer not from the internet, but from the records in your own CRM database.
-
2
The meeting note stays as a record, not as a summary
When you have the note written, Rapi posts it to the relevant record. The assistant's job does not end with producing a summary; the record itself changes, and you do not need to open the screen a second time.
-
3
Missing fields are not opened and filled one by one
You ask for fields such as tax number, industry or owner to be updated; Rapi updates the record. You are the one who says what is wanted. Rapi does not start a job on its own.
-
4
The quote → order step is already built into the product
The record action that turns a quote into an order is built into the product. The chain is not a flow the assistant invented; it is the product's own action.
-
5
Changes to existing records leave a trace
Every field Rapi changes on existing records lands in the field-level change history: when which field moved to which value (for protected fields, only a marker). The initial values of a record Rapi creates are not recorded there. The changes the AI makes stay auditable.
-
6
If the job runs long the assistant stops; it does not carry on by itself
The number of steps that can be taken in a single request is limited: at most eight. Rapi is not an agent running in the background; every job starts with a request you initiate and ends with that request.
The surface you rest on when you connect your own Claude
A connector you add in Claude
Your administrator turns on Claude in Setup › AI Connectors; you add the Rapitek connector in Claude and sign in with your own CRM account.
Access without sharing passwords
Access is granted with permissions; no connection is made by sharing a user password. You can withdraw the authorisation just as you granted it.
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, and you can read the field structure from outside.
Field structure read automatically
The field structure is read from the API; the connecting code does not have to track the field list by hand. When fields change, what is read changes with it.
Several operations in one request
More than one operation can be sent in a single request: up to 25 at a time; bulk transfers handle up to 200 records per request.
The change history covers the assistant too
Changes made through the assistant to existing records also land in the field-level change history; when which field moved to which value is visible (for protected fields, only a marker). The initial values of a record created through the assistant are not recorded there; the creator and creation time are set by the system and cannot be changed from the user screens, data import or the API.
Rapi, or your own Claude?
| Topic | Rapi: the assistant inside the product | The MCP connector: your own Claude |
|---|---|---|
| Where it runs | Inside the CRM: in the mobile app, alongside the record screens | In your own Claude client; it connects to the CRM without disturbing the way you already work |
| How it connects | Ready inside the product; no separate connection | You sign in with your own CRM account; Claude works within your permissions |
| How it is enabled | Built into the product; it works when you use it. An administrator can turn off all AI features in Setup › System Controls | Your administrator turns it on in Setup › AI Connectors; you add the connector in Claude and sign in with your own CRM account |
| Does it write records | Yes, it reads and writes; it creates and updates core records such as leads, contacts, companies and opportunities | The authorisation you grant determines the scope of access; you decide how much of it to open |
| What its limit is | At most eight steps in a single request; it does not run by itself in the background | Works with Claude; through the open MCP standard it is also designed to connect to ChatGPT (Developer Mode) and Gemini CLI |
| Where the request goes | When you use the assistant, to Anthropic's service in the United States | To Anthropic through your own Claude account; the contract on that side is between you and Anthropic |
What we have verified
How is the Claude side switched on?
-
1
The decision is yours
AI features send the relevant content to Anthropic only when you use them or when an automation set up by your administrator uses them. One switch under Setup › System Controls turns them all off.
-
2
We set the framework for the transfer in writing
When you use the assistant, requests go to Anthropic's service in the US. This is a second cross-border transfer on top of the hosting in the EU. Anthropic is named in the sub-processor list on our security page. We establish the basis for the transfer together during the contract process.
-
3
Connecting your own Claude
Your administrator turns on Claude in Setup › AI Connectors; you add the Rapitek connector in Claude and sign in with your own CRM account. Access is granted with permissions; no password is shared. You decide who connects and with what scope.
-
4
Auditing and turning it back off
Updates made through the assistant to existing records are tracked in the change history; the initial values of newly created records are not recorded there. If you change your mind, the assistant is turned off from the same place; the rest of the CRM carries on working exactly as it did.
Scope and setup terms
- Every job starts with your request. Rapi works on a request you initiate and takes at most eight steps per request; it does not run on its own in the background.
- The connector works with Claude. Because it supports the open MCP standard, it is also designed to connect with ChatGPT (Developer Mode), Gemini CLI and other MCP clients; for these clients, we set up the connection together with you.
- The assistant does not change the product's general limits. Stock synchronisation, an order-invoice-collection chain that flows on its own and production automation stay outside the scope, whether the assistant is on or off; the reasons are in the scope section of the integrations page.
Data location, and the second transfer here. Your data sits in the European Union: the database in Helsinki (Finland), the files and media you upload in Frankfurt (Germany), the database backups in Falkenstein (Germany). We have no component in Türkiye, and we have no such feature as region selection. The AI assistant adds a second cross-border transfer on top of this: when you use the assistant, requests go to Anthropic's service in the United States. That is why the decision stays with you: AI features send content only when you use them or enable them in an automation, and one switch under Setup › System Controls turns them all off. Audio recordings are transcribed on our own servers and are not sent to the AI provider. Seen from Türkiye, both transfers fall within the scope of Article 9 of Law No. 6698; we establish the basis for them together during the contract process and state in writing which component sits in which country. We named Anthropic, together with the country it is in and the condition under which it comes into play, in the sub-processor list on our security page.
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 forms and describe the architecture in writing.
Plan prices are out in the open; scope comes out in discovery
The Claude connection runs in the product today; Rapi AI credit, on the other hand, is a separately priced item. We publish plan prices and the separately priced items on a single page, with the figures.
Three plans, a scope table and the separately priced items on a single page.
Frequently asked questions about the Claude integration
Does AI really work in Rapitek CRM?
Which AI provider does Rapi run on?
Does Rapi only read, or does it write records too?
Can I connect my own Claude account to the CRM?
What is the MCP connector?
Does the connector also connect to ChatGPT or Gemini?
When do the AI features send my CRM data to an AI provider?
Does our data go to Anthropic?
How do we audit the changes the assistant makes?
Does Rapi work autonomously: does it do work by itself overnight?
Where is our data held?
Can we see it before we buy?
Let's look at the Claude side with your own data, in 30 minutes
In the intro call, let us show you Rapi writing records and how the Rapitek connector is added to your own Claude, using your scenario; and let's talk through the scope of the AI features together. Then we open your 7-day trial account; no credit card required.
