Integrations
Find where each kind of connection is documented, from a CSV import to the REST API and MCP.
Updated 23 September 2026
- Why
- The platform has to fit the systems a business already runs, not replace them overnight.
- What
- Connections tailored per product, custom REST connections, signed webhooks, a REST API and an MCP server.
- How
- An admin connects each one in Settings, and API keys scope every call to one organisation.
Where it appears
| Area | What you see | Brought by |
|---|---|---|
| AI | Connected email inboxes in the composer's Integrations menu | Every workspace |
| Suppliers | Price list imports and RFQs by email to any supplier | Source |
| Catalogue | CSV imports, a daily REST sync and the API's bulk upsert | Sales Engineer, Wizard, Commerce, Source and Stock |
| Stock | Stock lines, locations and movements over the REST API | Stock |
| Wizard | A wizard embedded on your own website with its own embed key | Wizard |
| Inspect | Contact finders on your own key and your own account | Inspect |
| Commerce | Your website's enquiries and activity sent in on a site key | Commerce |
Every plan can connect
Integrations are not a plan feature: the free plan can connect the same systems as any other. An admin connects them in Settings then Integrations. Ultra and Max also include hands on help wiring connectors up and keeping them running.
Where to read on
| You want to | Read |
|---|---|
| See every provider and its status | Connecting other systems, or Integrations on the website |
| Import or export a file | CSV import and export reference |
| Keep a catalogue in sync from another system | REST connections |
| Call Kabaido from your own code | API keys and scopes and the REST API |
| Hear about changes in your system | Webhooks |
| Post a status in from your ERP | Inbound endpoints |
| Work with an AI assistant of your own | MCP |
| Answer requests from your own inbox | The email agent |
Related
- Connecting other systemsRead any integration's label correctly and pick the right path for a system that has no named connection.
- API keys and scopesCreate a key that can do exactly what one integration needs, and retire it safely.
- The REST APICall every v1 resource with the right scope, page through lists and handle every error it returns.
- SettingsKnow what each settings section holds and who can open it.