Skip to content

Integrations

Kabaido works with the systems you already run

Kabaido sits alongside the ERP, CRM, accounting and messaging tools your team already uses. It reads what arrives, writes back to what you run and keeps a clean trail, so there is no migration and nothing to rip out. We work closely with you to connect whatever you run, and we keep it working.

What we connect to

The tools your team already uses

ERP, CRM, accounting, messaging and more. Every system below is labelled by exactly how it connects today, with nothing dressed up as a one-click connector when it is not. Do not see yours? We will build the connection with you and keep it supported.

Any system

If it has an API, a webhook or a file export, it connects to Kabaido. The generic framework reaches systems that have no named connector yet.

Set up with you

We help you map fields, prove a feed with a dry run, then get the first sync live. You are never handed a blank screen.

Kept working

Every delivery leaves a receipt, so a broken sender shows at once, and we keep your connections running as your tools change.

Works today
Works end to end inside Kabaido today.
Template
A prefilled template over the generic framework; you supply your own credentials.
Via automation
Works today through Zapier, Make or n8n plus the Kabaido API.
Roadmap
A named connector is planned; the API and webhooks work now.

AI assistants

  • ClaudeWorks today
  • Any MCP clientWorks today

Messaging

  • SlackWorks today
  • Microsoft TeamsWorks today

Automation

  • ZapierVia automation
  • MakeVia automation
  • n8nVia automation

ERP

  • SAP Business OneRoadmap
  • Dynamics 365 Business CentralTemplate
  • OdooVia automation
  • NetSuiteRoadmap

Accounting

  • XeroVia automation
  • QuickBooksVia automation
  • SageRoadmap

CRM

  • HubSpotTemplate
  • SalesforceVia automation

Data in and out

  • CSV import and exportWorks today
  • Custom REST connectionWorks today
  • Custom inbound endpointWorks today
  • Email-inRoadmap

The systems our customers depend on shape what we connect next. If you do not see yours, tell us what you run and we will prioritise it.

At a glance

Find your stack by category

The same four labels as the directory above, summarised by system category so you can place your stack in seconds.

How the named systems in each category connect to Kabaido today.
System categoryHow it connects todayNamed systems
ERPTemplateVia automationRoadmapSAP Business One, Dynamics 365 Business Central, Odoo, NetSuite
CRMTemplateVia automationHubSpot, Salesforce
AccountingVia automationRoadmapXero, QuickBooks, Sage
MessagingWorks todaySlack, Microsoft Teams

MCP

Ask Claude about your own catalogue, quotes and orders

Your team reads live commercial data and raises a request without leaving the assistant they already use. Kabaido runs a streamable HTTP MCP server at /api/mcp that any MCP client can reach: Claude, Claude Code, Cursor and the rest.

The server exposes nine tools, one of which writes. Reads search the catalogue and fetch quotes, orders, customers and requests. The single write tool opens a request from RFQ or enquiry text, which the team then sees in Requests for the AEI to turn into a quote. Each tool checks its scope on every call, so a read-only key can never write. The full tool reference and set-up steps for each client live in the MCP connector guide.

There are two ways to authenticate: an organisation API key, or sign-in with claude.ai. Both are scoped to your role in the organisation, and the deeper flow is documented for your security team.

Reads are free; work actions through a connector meter at twice the base credit weight.

Reads cost nothing. The write action meters at twice the base credit weight, the same way a request raised inside Kabaido does. See how credits work on the pricing page.

API

Push your catalogue in and pull quotes and orders out

Move products in bulk from the system that owns them, then read every quote, order, customer and request back into your own tools. Public v1 REST with Bearer organisation keys, all on kabaido.ai, so there is no second API origin to allowlist.

Bulk product import is the usual first step. The same payload runs from the Catalog with mapping, validation and a dry run, so you can prove a feed before you automate it.

Nine scopes

  • products:read
  • products:write
  • quotes:read
  • quotes:write
  • orders:read
  • customers:read
  • customers:write
  • requests:read
  • requests:write

Every area can be read. You can write products, quotes, customers and requests today; orders are read-only for now. A key holds any subset of these scopes.

Rate limit
600 requests per minute per key.
OpenAPI 3.1
The full document is public at /api/v1/openapi.json and the API reference walks every endpoint.
Money in minor units
Every amount is an integer in minor units with a currency code alongside, never a float. Formatting happens at the edge.
Keyset pagination
List endpoints paginate by keyset; pass the opaque next_cursor back to continue exactly where you left off.
Quotes API
Request
curl "/api/v1/quotes?limit=2" -H "Authorization: Bearer kbd_..."
Response
  • Q-26-00026£528.96inc VATvalid until 11 JulDraft
  • Q-26-00025£202.08inc VATvalid until 10 JulDraft

Money in minor units. 600 requests per minute per key.

Webhooks and inbound

Events out, requests in

Your systems hear about work as it happens and can open work in return.

Webhooks out

Five events, delivered as they happen:

  • quote.created
  • quote.sent
  • quote.accepted
  • order.created
  • service_item.updated

Every delivery is HMAC signed with the X-Kabaido-Signature header in its t and v1 scheme and retried up to five times. Choose the body per endpoint: the signed JSON envelope, a Slack message or a Teams Adaptive Card. The signature header is sent in every format.

Inbound endpoints

A tokenised /api/in/ URL any system can post JSON to. Each endpoint maps to exactly one action: create_request, upsert_customers or upsert_products. Every delivery leaves a receipt under the endpoint in Settings, so a misconfigured sender is visible immediately, and pausing or deleting the endpoint revokes the URL at once.

Any systemPOST JSON/api/in/<token>one mapped actioncreate_requestupsert_customersupsert_products

Meet your systems where they are

Kabaido does not ask you to migrate. It reads what arrives, writes back to what you run and keeps a clean trail.