Configure Your Own OAuth Clients

Custom OAuth clients apply workspace-wide for the specific integration. All new connections will use your OAuth application once configured.

How Custom OAuth Works

When you configure a custom OAuth client, Langdock routes all authentication flows through your OAuth application instead of the default Langdock client. This means:

Your branding (custom name and logo) appears in consent screens
Your tenant policies control user access and admin consent requirements
Your rate limits apply to API calls made by your users

Create OAuth App at Provider

Register a new OAuth application in your provider’s developer portal (Google Cloud Console, Microsoft Azure, etc.).Required Configuration:

Copy the exact redirect URL from Langdock’s integration settings
Select all required scopes shown in Langdock for that integration
Configure any tenant-specific settings (admin consent, allowlisting)

Gather Credentials

Note down the following from your OAuth app:

Client ID (always required)
Client Secret (always required)
Tenant ID or Domain (required for some providers like Microsoft)

Configure in Langdock

Navigate to Settings → Integrations and select your target integration.

View the current configuration next to the integration and enable all required scopes in your own OAuth client. Scopes that are not added to your client will cause an insufficient scopes error.

Close this screen, click on the integration, and in the OAuth client dropdown, select Configure your own

Paste your Client ID and Client Secret, and click Save

Test Authentication

Have a user connect their account to verify:

Consent screen shows your client
Required scopes are granted
Data access works as expected through actions

Integration Settings Interface

When configuring a custom OAuth client, you’ll see these fields:

Redirect URL
Required Scopes
Credentials

Copy this exact URL to your OAuth app’s redirect URI configuration. The URL format is:

https://app.langdock.com/api/integrations/{integration-id}/callback

The redirect URL must match exactly. Any mismatch will cause redirect_uri_mismatch errors.

Each integration displays the specific OAuth scopes needed for full functionality. For example, Gmail requires:

https://www.googleapis.com/auth/gmail.send
https://www.googleapis.com/auth/gmail.compose
https://www.googleapis.com/auth/gmail.readonly
https://www.googleapis.com/auth/gmail.labels
https://www.googleapis.com/auth/gmail.modify

Copy these scopes to your OAuth app configuration. Scopes that are not added to your client will cause an insufficient scopes error.

Behavior and Impact

Workspace-Wide Changes

All new connections use your custom OAuth client
Existing connections continue working until users reconnect
Only affects the specific integration you configured

User Experience

Users see your app name and branding in consent screens
Authentication flows redirect through your OAuth application
Your app’s rate limits and quotas apply to user requests

Common Configuration Errors

redirect_uri_mismatch

Cause: Redirect URL doesn’t match exactly between Langdock and your OAuth appSolution:

Copy the redirect URL from Langdock exactly
Check for trailing slashes or protocol mismatches
Verify you’re configuring the correct environment

invalid_client

Cause: Client ID or Client Secret is incorrectSolution:

Double-check credentials from your OAuth app
Ensure no extra spaces or characters
Verify the client is enabled in your provider’s console

consent_required

insufficient_scope

Cause: Missing required scopes in your OAuth appSolution:

Add all scopes shown in Langdock to your OAuth app
Users may need to reconnect after adding scopes
Verify scope names match exactly (case-sensitive)

Managing Existing Connections

When switching from Langdock’s default client to your custom OAuth client:

Existing user connections may require re-authentication. We suggest notifying your users upfront.

Migration Steps

Configure your custom OAuth client
Notify users about the upcoming change
Save the new OAuth configuration
Users reconnect their accounts when prompted
Verify all connections work with your custom client

Keep your OAuth app credentials secure and limit access to organization admins only.

Integrations Requiring Your Own OAuth Client

Some of our integrations can only be used when providing your own OAuth client. Details on how to connect them with Langdock are described in this section.

ServiceNow

Show how to configure a ServiceNow OAuth client

Required authentication fields

Provide ServiceNow Subdomain

When a user wants to create a connection with ServiceNow, they have to provide the subdomain of your ServiceNow instance.

ServiceNow Integration Requirements

Are self-hosted or cloud-hosted accounts supported?

Only Cloud-hosted accounts are currently supported.

Is a paid ServiceNow plan required?

A paid ServiceNow account is required to create an application registry. View ServiceNow’s plans here.

Are any special account permissions / roles required?

Yes. To connect by OAuth, your systems administrator should set up the right configuration within your instance to connect any user using an OAuth connection. E.g. all users need the oauth_user role to be able to connect. Learn more about ServiceNow’s groups and permissions

Are there usage limits?

Yes. ServiceNow implements rate limiting to prevent excessive API usage. System administrators can configure rules that restrict the number of inbound REST API requests processed per hour. Learn more about ServiceNow’s usage limits.

Configuring a Snowflake OAuth Client

Configuring your own OAuth client for Snowflake gives you control over authentication policies, token validity periods, and IP allowlisting within your Snowflake environment.

Show how to configure a Snowflake OAuth client

Required Information:

OAuth Redirect URL: Copy this from Langdock’s Snowflake integration settings page
Client ID: Generated by Snowflake after creating the security integration
Client Secret: Generated by Snowflake after creating the security integration
Authorization URL: Your Snowflake account’s authorization endpoint

The Redirect URL from Langdock must be provided in Snowflake, while the Client ID, Client Secret, and Authorization URL from Snowflake must be entered into Langdock’s integration settings.

If your Snowflake account has network policies or IP allowlisting enabled, you may need to whitelist Langdock’s static IP address to allow connections. See Static IP Configuration for details.

Setup Guide

Create Integration in Langdock

In your Langdock workspace, create your new Snowflake integration, and set up a custom OAuth Client.

Show how to set up a custom OAuth client in Langdock

Navigate to Integrations in Langdock
Click “Add Integration” and select “Start from Scratch”
Fill in your preferred name and description for your new Snowflake integration
Click “Create”
Authentication Type: Select “OAuth 2.0” from the dropdown
Authentication fields: Leave blank
OAuth Configuration: Save your OAuth Redirect URL

Create Security Integration in Snowflake

In Snowflake, select your workspace, and create a new security integration.

Show how to create a new security integration in Snowflake

Create a new .sql file, and paste the following query:

CREATE SECURITY INTEGRATION <integration_name>
  TYPE = OAUTH
  ENABLED = TRUE
  OAUTH_CLIENT = CUSTOM
  OAUTH_CLIENT_TYPE = CONFIDENTIAL
  OAUTH_REDIRECT_URI = '<your_redirect_uri>'
  OAUTH_ISSUE_REFRESH_TOKENS = TRUE
  OAUTH_REFRESH_TOKEN_VALIDITY = 86400;

Replace <integration_name> with a descriptive name and <your_redirect_uri> with the OAuth Redirect URL from Step 1.
Run the query to create your new security integration in Snowflake. Note: Adjust your OAUTH_REFRESH_TOKEN_VALIDITY value based on your security policies.

Retrieve Client ID and Client Secret

Show how to retrieve your Client ID, and Secret from Snowflake

Within the same workspace, run the following query:

SELECT SYSTEM$SHOW_OAUTH_CLIENT_SECRETS('<integration_name>');

Replace <integration_name> with the name you gave your security integration in the previous step.
Save your Client ID and Client Secret. Store these credentials securely as they provide access to your Snowflake account.

Retrieve Account URL from Snowflake

Show how to retrieve your Account URL from Snowflake

Click on your account name in the bottom left corner of your Snowflake application
Under the Account Section, click on “View Account Details”
Copy your Account URL

Configure Integration Settings in Langdock

Show how to configure your Snowflake OAuth client in Langdock

Add your Client ID and Client Secret from Step 3 in the respective input fields of your new Langdock integration
In the following sections:
- Authorization URL
- Access Token URL
- Refresh Token URL
Replace only https://example.com with your Snowflake Account URL from Step 4.

Example:

https://example.com/oauth/authorize

Becomes:

https://<your-snowflake-account-url>/oauth/authorize

Click Save

Test the Connection

Show how to add a Connection to your Snowflake Integration

Click “Add Connection” in your Snowflake integration.

You should be directed to the Snowflake Authorization screen
Log into your Snowflake account

You have now successfully set up your own OAuth Snowflake integration!

Prompt Engineering

Product Guides

AI Adoption & Rollout

Resources

Configure Your Own OAuth Clients

How Custom OAuth Works

Integration Settings Interface

Behavior and Impact

Workspace-Wide Changes

User Experience

Common Configuration Errors

Managing Existing Connections

Migration Steps

Integrations Requiring Your Own OAuth Client

ServiceNow

ServiceNow Integration Requirements

Configuring a Snowflake OAuth Client

Setup Guide

Prompt Engineering

Product Guides

AI Adoption & Rollout

Resources

​How Custom OAuth Works

​Integration Settings Interface

​Behavior and Impact

​Workspace-Wide Changes

​User Experience

​Common Configuration Errors

​Managing Existing Connections

​Migration Steps

​Integrations Requiring Your Own OAuth Client

​ServiceNow

​ServiceNow Integration Requirements

​Configuring a Snowflake OAuth Client

​Setup Guide

How Custom OAuth Works

Integration Settings Interface

Behavior and Impact

Workspace-Wide Changes

User Experience

Common Configuration Errors

Managing Existing Connections

Migration Steps

Integrations Requiring Your Own OAuth Client

ServiceNow

ServiceNow Integration Requirements

Configuring a Snowflake OAuth Client

Setup Guide