Integrations

Find where keys, webhooks, inbound endpoints and customer connections are created and where a Claude connection is revoked.

Updated 11 November 2026

Why: The systems around Kabaido change more often than Kabaido does, so every connection has to be visible and revocable in one place.
How: Open /app/settings/integrations. It needs the Admin role or above.

What is managed here

Entry	What you do there	Reference
Kabaido API	Create and revoke scoped API keys.	API keys and scopes
Custom outbound webhook	Add endpoints that receive signed events, see recent deliveries and retry one. The Slack and Microsoft Teams entries add the same endpoint with a readable message format and the automation platform entries add it for a platform's own webhook URL.	Webhooks
Custom inbound endpoint	Create a URL another system can post JSON to, choose its action and see recent receipts.	Inbound endpoints
Customer connections	Pull customers from another system's REST endpoint, on a daily sync or by hand with Run now. The fetch is tested before anything is written and the credentials are stored encrypted.	Customers
Claude	See the connections your people have approved for the connector, with when each was last used and when it expires. Revoke one here. The Any MCP client entry lists the same connections. The connector takes no API key: each person signs in.	Adding the connector

Product feeds from another system are set up in the Catalogue, not here. How an ERP is connected is agreed at implementation: see ERP options.

An API key, a webhook signing secret and an inbound endpoint's secret are each shown once, at creation. Kabaido cannot show one again: create a new one.
Deleting a webhook endpoint stops its events at once and destroys its signing secret.
Deleting a customer connection keeps the customers already pulled in and destroys the saved credentials.

Missing today: the design engine panel has no Integrations section. Its Claude section records what came through the connector.