Skip to content
Integration · Claude

If you use Claude, your CRM talks to Claude.

Yes, Rapitek CRM works with Claude: it runs as a custom connector in Claude's web, desktop and mobile apps; you sign in with your CRM account, and Claude reads and writes within your permissions. This connection runs in production today; setting it up does not require a provider-specific project. Rapi, the assistant inside the product, also does not only read the CRM: it writes records too.

Rapitek CRM channels and integrations screen (Turkish interface): Claude Connector, WhatsApp Bots, Email Accounts, Meta Pages, CTI Adapters and Payment Providers cards
The Claude Connector among the integration cards

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 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. The connector works in Claude's web, desktop and mobile apps. Within your permissions, Claude reads and writes your records and sends messages with your approval: on WhatsApp (personal and business line; on the business line, an approved template for a new contact or a conversation past 24 hours), by email (a reply in the same thread; open and click tracking on marketing email) and on Instagram (a reply in an open conversation within the 24-hour window). Consent and opt-out rules apply to these sends automatically. 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 and the field structure can be read from outside. In the connector each call handles one record; bulk operations belong to the REST API.

We wrote up our general approach to integrations with the same openness on the integrations page.

A concrete scenario

Wednesday 11:15, a quote is being prepared. With Rapi turned on, this is what changes:

  1. 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. 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. 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. 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. 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. 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.

Bulk operations

In the Claude connector each call handles one record. Bulk operations belong to the REST API that integrators use: 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.

Two separate routes

Rapi, or your own Claude?

These are two different things and they are set up separately: Rapi is built in; your administrator turns on the Claude connector in Setup › AI Connectors. You can also use both together.
TopicRapi: the assistant inside the productThe MCP connector: your own Claude
Where it runsInside the CRM: in the mobile app, alongside the record screensIn your own Claude client; it connects to the CRM without disturbing the way you already work
How it connectsReady inside the product; no separate connectionYou sign in with your own CRM account; Claude works within your permissions
How it is enabledBuilt into the product; it works when you use it. An administrator can turn off all AI features in Setup › System ControlsWith AI features on 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 recordsYes, it reads and writes; it creates and updates core records such as leads, contacts, companies and opportunitiesThe authorisation you grant determines the scope of access; you decide how much of it to open
What its limit isAt most eight steps in a single request; it does not run by itself in the backgroundWorks with Claude; in ChatGPT (chatgpt.com) it also reads and queries records
Where the request goesWhen you use the assistant, to our AI provider in the United StatesTo Anthropic through your own Claude account; the contract on that side is between you and Anthropic
What we can say

What we have verified

Your own account
Add the connector in Claude and sign in with your CRM account
Reads and writes
Rapi does not stop at fetching records; it creates and updates core CRM records
At most 8 steps
Steps allowed in one request; not autonomous: you start the request
One switch
An administrator turns off all AI features with one switch in Setup
EU
Database Helsinki, files Frankfurt, backups Falkenstein; AI provider US
Implementation

How is the Claude side switched on?

  1. 1

    The decision is yours

    AI features send the relevant content to our AI provider in the United States 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. 2

    We state the transfer openly

    When you use the assistant, requests go to our AI provider 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. 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. 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, AI features and the connector are turned off in Setup › System Controls; the rest of the CRM keeps working.

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. It works with ChatGPT too: it is added on chatgpt.com as a custom connector and reads and queries your records; 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). The AI assistant adds a second cross-border transfer on top of this: when you use the assistant, requests go to our AI provider 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 the provider, 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; the Rapi AI usage allowance, 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.

FAQ

Frequently asked questions about the Claude integration

Is there a CRM that works with Claude?
Yes. Rapitek CRM works with Claude: add the Rapitek connector in Claude and sign in with your own CRM account. Claude reads and writes your records within your permissions. The connection runs in production today in Claude's web, desktop and mobile apps. From Claude you send WhatsApp messages (personal and business line; on the business line, an approved template for a new contact or a conversation past 24 hours), new emails and replies in the same thread, and Instagram replies within the 24-hour window; consent and opt-out rules apply automatically, and the connector does not do bulk sends. Your administrator switches it on under Setup › AI Connectors.
Does AI really work in Rapitek CRM?
Yes, in two separate forms. Rapi, the assistant inside the product, reads and writes CRM records. The second route is the MCP connector: you add the Rapitek connector in Claude and sign in with your own CRM account. Both work in the product today; no provider-specific development project is needed.
Does Rapi need a separate connection?
No. Rapi is built into the product; it sends content only when you use it or when an automation enables it, and an administrator can turn off all AI features with one switch in Setup › System Controls. When you use it, the assistant's requests go to our AI provider in the United States; we wrote up what that means in KVKK terms in the limits section.
Does Rapi only read, or does it write records too?
It reads and writes. It fetches, creates and updates core records such as leads, contacts, companies and opportunities. The changes it makes to existing records land in the product's field-level change history, which means those changes can be audited one by one afterwards; the initial values of a record it creates are not recorded there.
Can I connect my own Claude account to the CRM?
Yes. Your administrator turns on Claude in Setup › AI Connectors; you add the Rapitek connector in Claude as a custom connector and sign in with your own CRM account. The connector works in Claude's web, desktop and mobile apps. Within your permissions, Claude reads and writes your records and sends messages with your approval. Access is granted with permissions, and no user password is shared. From Claude you can also read your reports and dashboards and open a support ticket. A send is a real message; Claude sends it at your request. Consent and opt-out rules apply automatically: no message goes to a person who has opted out or is blocked. Marketing email open and click tracking can be switched on. These work in accounts where AI features are switched on.
What is the MCP connector?
It is a connector that introduces the CRM to an AI client. The connector rests on the same surface integrators use: a REST API where access is granted with permissions rather than shared passwords, the field structure can be read from outside. In the connector each call handles one record; bulk operations belong to the REST API. In other words, the assistant does not look into the CRM from outside the scope the API permits.
Does the connector also connect to ChatGPT or Gemini?
The connector works with Claude. It works with ChatGPT too: it is added on chatgpt.com as a custom connector, you sign in with your CRM account, and it reads and queries your records; we set up the connection together with you. Gemini CLI, Gemini Enterprise and Gemini's consumer app cannot connect to the connector today; the Gmail and Google Calendar connections work today.
When do the AI features send my CRM data to an AI provider?
Only when you use an AI feature or your administrator enables it in an automation. The Rapi assistant, business card scanning, meeting analysis, the WhatsApp/Instagram assistant and the AI step in flows send the relevant content to our AI provider in the United States. Audio recordings are transcribed on our own servers; the audio file is 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.
Does our data go to the AI provider?
When you use the assistant, the content the request requires goes to our AI provider in the United States. Where your CRM data sits does not change: database in Helsinki, files in Frankfurt, backups in Falkenstein, but the assistant adds a second cross-border transfer on top of the hosting in the EU. Seen from Türkiye, this too falls within the scope of Article 9 of Law No. 6698; we establish the basis for it together during the contract process.
How do we audit the changes the assistant makes?
From the field-level change history. Changes made through the assistant to existing records also land in this audit trail: 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 in it. The AI does not use a separate route that skips the product's audit trail.
Does Rapi work autonomously: does it do work by itself overnight?
No. Every job starts with a request you initiate, and the number of steps that can be taken in a single request is limited: at most eight. We do not offer an agent that runs indefinitely in the background and sets its own goals.
Where is our data held?
In the European Union: the database in Helsinki (Finland), the files you upload in Frankfurt, the database backups in Falkenstein (Germany). Your CRM data is held in a separate database that belongs to you. When you use Rapi or other AI features, or enable them in an automation, the relevant content is sent to our AI provider in the United States for processing.
Can we see it before we buy?
Yes. You can try it free for 7 days: fill in the form and we'll open your trial account and send you your login details. If you like, we can also start with a 30-minute intro call. In that call we show the assistant writing records and how the Claude connector is added, using your own scenario.

Let's look at the Claude side with your own data, in 30 minutes

Fill in the form and we'll open your 7-day trial account and send you your login details; no credit card required. If you like, in a 30-minute intro call we show you Rapi writing records and how the Rapitek connector is added to your own Claude, using your scenario, and talk through the scope of the AI features together.

Made with RapitekGO

We'd like to use optional measurement cookies; if you decline, the site works the same. Cookie policy