IntegrationsCRM
Overview
Keep your CRM in step with Kaiten — a connector mirrors Kaiten customers and instances into the CRM, with Kaiten as the source of truth. Attio is available today.
Kaiten holds the commercial contract — who your customers are, where your product runs for them, and under which License. Your sales and customer-success teams work in a CRM. A CRM connector keeps the second in step with the first, so nobody copies a customer from one tool to the other.
One direction: Kaiten → CRM
A connector mirrors Kaiten into the CRM, and only that way. Kaiten is the source of truth for customers and instances: it creates their records in the CRM, keeps them up to date, and reads nothing back.
| In Kaiten | In the CRM |
|---|---|
| A Customer is created or updated | A company record is created or updated |
| An Instance is created or updated | A record of that instance is created or updated, linked to its company |
| Fields you choose to map — the License name and type, the License dates, the deployment zone, the lifecycle stage | Attributes of that record |
The direction is deliberate. One system owns the creation of a record and the other follows it: no sync loop, no conflicting edit, and no reconciliation job to trust.
The link between the two records
Each mirrored record keeps a permanent link: the CRM's record ID is stored on the Kaiten Customer or Instance as the external_id of its integration link for that CRM, with the state of the last sync. The link is what makes the sync converge instead of duplicating: an update finds the record it wrote before. The console shows it in the CRM Sync column of the Customers and Instances lists.
Connectors
A CRM connector ships inside Kaiten and runs on the event stream. It stays inert until your organization connects it — and connecting it can be gated by your License: connectors explains the three states.
Attio
Available. Customers become Companies, instances become Workspace records, with the fields you map.
HubSpot Coming soon
On the roadmap. Its documentation lands with the connector.
Salesforce Coming soon
On the roadmap, after HubSpot.
Coming soon
Two extensions are on the roadmap Coming soon, and neither is available today:
- CRM → Kaiten. A deal won in the CRM creating the Customer and its Instance in Kaiten, for teams whose CRM owns the customer record.
- Usage and renewal signals. Usage against the grants and threshold crossings written onto the company record.
Your CRM is not listed, or you need one of these today? Every change the connectors act on is a domain event: webhooks on Kaiten Cloud and the event stream on a self-hosted stack deliver all of them, and the integration link above is open to your own integration through the API.
Where to go next
Using Attio: connect it. Building your own sync: start from the event catalog.
Verifying Signatures
Every Kaiten Cloud webhook delivery is signed. Verify the signature with the Svix SDK before trusting a payload — headers, snippets for Node.js, Python, and Go, and where the secret lives.
Attio
Mirror Kaiten customers and instances into Attio — connect with an API token, choose a sync policy, map fields onto attributes of your workspace, and follow each record's sync state.