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.
| 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
- 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.
Named ERP and CRM connectors and inbound email per organisation are roadmap items, stated plainly rather than implied. The generic surfaces above cover the same data today.