Skip to content

Connecting other systems

Read any integration's label correctly and pick the right path for a system that has no named connection.

Updated 23 September 2026

Why
Your workshop already runs systems, and Kabaido has to meet them rather than replace them.
How
Open /app/settings/integrations, search for what you run and open its entry.
Settings then Integrations: every connection grouped by kind, each with its status label.
/app/settings/integrations, demonstration data, captured 23 September 2026. Open full size

The four labels

Every entry carries exactly one label, on the website and in Settings alike. Nothing is labelled Works today unless Kabaido code talks to the provider.

LabelWhat it means
Works todayKabaido code talks to the provider.
TemplateA prepared recipe on a generic path, which you finish.
Via automationThrough Zapier, Make or n8n.
RoadmapNot built yet. Tell us what you need and we will talk it through.

Finding an entry

  1. Step 1.

    Open /app/settings/integrations. Every connection sits in one list with a search box, a type filter and the All, Active, Suggested and New chips.

  2. Step 2.

    Open an entry. Its panel says what it is for, walks through the setup and, once connected, manages it: keys, endpoints, deliveries or receipts.

  3. Step 3.

    A link ending ?open=<id> opens one panel directly, which is how prompts elsewhere in the platform send you there.

Connecting needs the admin role or above. No plan gates a connection; an entry tied to a product, such as the Inspect contact finders, needs that product switched on.

The universal paths

When your system has no named entry, one of these reaches it. Most setups use two or three together.

If your systemUse
Can be programmed against an APIThe REST API with a scoped key, or the MCP server for an AI assistant.
Needs to hear when something happens hereOutbound webhooks: signed JSON posted to your URL.
Can send but not receiveAn inbound endpoint: a tokenised URL it posts JSON to.
Answers a GET request from the internetA scheduled REST pull: customers or products, daily or by hand.
Is a person with a spreadsheetCSV import and export, on every plan.
Already runs an automation toolZapier, Make or n8n: webhooks start a flow and the flow writes back over the API.

A Roadmap entry is not built. Its page says what it would do; tell us what you need, and meanwhile the paths above cover the same data.