Connecting other systems
Know exactly which integrations are native, which run through automation tools and which are roadmap.
The integrations directory in Settings is graded honestly. Every entry carries one of four statuses, so you always know what works today versus what is planned.
How the directory works
Settings, Integrations is one list rather than a set of tabs: every integration Kabaido knows about, whatever kind it is, in one place with a search box, a type filter, sort and filter chips. Opening an entry slides in a panel carrying what that integration is for, its guided setup and, once it is connected, its own live management: keys, endpoints, event subscriptions, delivery history, whatever that kind of connection has.
Every connection you make is filed under the entry that made it, so the panel you set something up in is the panel you manage it from. Where a connection was made before that attribution existed, or genuinely is bespoke, it lists under a generic Custom entry for its kind, which is accurate rather than tidy. A link with ?open=<id> opens a panel directly, which is what the setup prompts elsewhere in the platform use.
| Status | Meaning |
|---|---|
| Native | Works end to end in Kabaido today. |
| Preset | A prefilled template over the generic REST framework; you supply the credentials. |
| Automation | Works now through Zapier, Make or n8n using the Kabaido API and webhooks. |
| Roadmap | A named connector is planned. The API and webhooks already cover the data. |
Native today
- Gmail and Microsoft 365 inboxes, through the email agent: enquiries answered where they arrive.
- Claude and any MCP client, through the MCP connector.
- Slack, as formatted messages through an outbound webhook in Slack format.
- Microsoft Teams, as Adaptive Cards through an outbound webhook in Teams format.
- Any REST API you control, through product and customer connections.
- Any system that can post JSON, through inbound endpoints.
- CSV import and export, everywhere, on every plan.
Automation platforms
Zapier, Make and n8n connect today using an API key and a webhook endpoint: webhooks push Kabaido events into a flow, and the flow writes back over the REST API. No Kabaido specific app is required.
Choosing a direction
Almost every integration question comes down to which end initiates, and that is usually decided by your network rather than by preference.
| If your system | Use |
|---|---|
| Can answer a GET request from the internet | A product or customer connection. Kabaido pulls, on a schedule, and you configure nothing at the other end. |
| Can send but not receive | An inbound endpoint. Your system posts JSON to a tokenised URL. |
| Can be programmed properly | The REST API with a scoped key. Full read and write, paginated, with real error codes. |
| Needs to know when something happens here | A webhook. Kabaido posts signed events to a URL you control. |
| Is a person with a spreadsheet | CSV. It is on every plan and it is nobody's second-class path. |
The five are not alternatives to one another so much as different halves of the same job. A typical setup pulls the catalogue in on a nightly connection and pushes quote and order events back out over webhooks.
Named ERP and CRM connectors are roadmap items, stated plainly rather than implied. The generic surfaces above cover the same data today, and a roadmap connector will be a preset over the same framework rather than a different mechanism.