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.
Create an OAuth app
Section titled “Create an OAuth app”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/callbackIntegrations that use an API key, basic credentials, or client credentials need no app: users enter their credentials when they connect.
| Provider | Setup guide |
|---|---|
| Box | OAuth 2.0 Setup |
| Dropbox | App Console |
| GitHub | Creating an OAuth App |
| GitLab | OAuth Provider |
| Google Drive | OAuth 2.0 Protocol |
| Jira | Jira REST API Authentication |
| Linear | OAuth 2.0 Authentication |
| Microsoft (OneDrive, Entra ID, Teams, Outlook) | Register an App |
| Slack | Creating an App |
Turn an integration on
Section titled “Turn an integration on”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:
kindo integrations listTo enable one, by its name, such as linear:
kindo integrations enable <name>Apply the change:
kindo config applyConfirm the result in Kindo under Command Center > Integrations.
Turn an integration off
Section titled “Turn an integration off”Disabling an integration keeps its existing connections.
kindo integrations disable <name>Apply the change:
kindo config applyChange an integration’s OAuth credentials
Section titled “Change an integration’s OAuth credentials”Edit them in the config:
kindo config editApply the change to the integrations only:
kindo config apply --only integrationsA 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.
Remove an integration completely
Section titled “Remove an integration completely”Turn it off, as above. Then delete its integration in Nango’s dashboard. To see the dashboard’s address, username and password:
kindo logins --show-secretsLet 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:
kindo config set overrides.serviceEnv.api.MICROSOFT_DELEGATED_SIGN_IN=per-connectionApply the change:
kindo config applySet up integration webhooks
Section titled “Set up integration webhooks”Integration Event triggers need the provider to send webhooks; Direct Webhook URL triggers don’t. Jira needs no setup. For Linear:
-
In Linear, go to Settings > API, open your OAuth app, and select Edit Application from its menu.
-
Turn on Webhooks, enter this URL, and select Issues under data change events:
https://api.<domain>/webhook/integration-connection/linear -
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.
