Skip to content
These docs are a preview of Self-Managed Kindo 2026.11, an upcoming release.

Set up integrations

Kindo ships a catalog of integrations, and you choose which ones are on. An organization’s Admins choose who can use each one; see Tool Action Access Controls.

For an integration that signs in with OAuth, create an OAuth app with the provider before you turn the integration on, with this callback URL:

https://integrations-api.<domain>/oauth/callback

Integrations that use an API key, basic credentials, or client credentials need no app: users enter their credentials when they connect.

ProviderSetup guide
BoxOAuth 2.0 Setup
DropboxApp Console
GitHubCreating an OAuth App
GitLabOAuth Provider
Google DriveOAuth 2.0 Protocol
JiraJira REST API Authentication
LinearOAuth 2.0 Authentication
Microsoft (OneDrive, Entra ID, Teams, Outlook)Register an App
SlackCreating an App

An integration that signs in with OAuth asks for its OAuth app’s client ID and secret when you enable it.

To list the integrations, with the name of each in the Integration column:

Terminal window
kindo integrations list

To enable one, by its name, such as linear:

Terminal window
kindo integrations enable <name>

Apply the change:

Terminal window
kindo config apply

Confirm the result in Kindo under Command Center > Integrations.

Disabling an integration keeps its existing connections.

Terminal window
kindo integrations disable <name>

Apply the change:

Terminal window
kindo config apply

Change an integration’s OAuth credentials

Section titled “Change an integration’s OAuth credentials”

Edit them in the config:

Terminal window
kindo config edit

Apply the change to the integrations only:

Terminal window
kindo config apply --only integrations

A new secret for the same OAuth app keeps existing connections working. A different OAuth app, with a new client ID, requires users to reconnect. Their connections stop working when their access tokens next refresh.

Turn it off, as above. Then delete its integration in Nango’s dashboard. To see the dashboard’s address, username and password:

Terminal window
kindo logins --show-secrets

Let users sign in to Microsoft per connection

Section titled “Let users sign in to Microsoft per connection”

Users can connect Microsoft integrations to their own single tenant, entering their Microsoft domain or tenant ID when they connect. To allow it, set this on the API:

Terminal window
kindo config set overrides.serviceEnv.api.MICROSOFT_DELEGATED_SIGN_IN=per-connection

Apply the change:

Terminal window
kindo config apply

Integration Event triggers need the provider to send webhooks; Direct Webhook URL triggers don’t. Jira needs no setup. For Linear:

  1. In Linear, go to Settings > API, open your OAuth app, and select Edit Application from its menu.

  2. Turn on Webhooks, enter this URL, and select Issues under data change events:

    https://api.<domain>/webhook/integration-connection/linear
  3. Copy the webhook signing secret. In Nango’s dashboard, paste it into the Linear integration’s Webhook Secret, and save. To see the dashboard’s address, username and password, run kindo logins --show-secrets.

Delete and reconnect, in Kindo, any connection created before you set up webhooks.