Skip to main content
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
1

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)
2

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)
3

Configure in Langdock

Navigate to Settings → Integrations and select your target integration.Byo Oauth 1 PnView 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.Byo Oauth 2 PnClose this screen, click on the integration, and in the OAuth client dropdown, select Configure your ownByo Oauth 3 PnPaste your Client ID and Client Secret, and Click SaveByo Oauth 4 Pn
4

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.

​
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

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
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
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

  1. Configure your custom OAuth client
  2. Notify users about the upcoming change
  3. Save the new OAuth configuration
  4. Users reconnect their accounts when prompted
  5. 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

⌘I