Custom OAuth Apps
Register your own OAuth applications for branded consent screens and custom scopes.
By default, Weavz provides pre-configured OAuth credentials for supported integrations. Custom OAuth apps let you use your own OAuth application credentials instead, giving you control over branding, scopes, and consent screens.
Why Use Custom OAuth Apps
- Branded consent screens — users see your app name instead of "Weavz"
- Custom scopes — request only the permissions your app needs
- Different environments — separate OAuth apps for development, staging, and production
- Compliance — some organizations require using their own OAuth credentials
- Rate limits — use your own API quota instead of shared platform limits
Registering an OAuth App
Step 1: Create the App with the Provider
First, create an OAuth application in the third-party service's developer portal:
- Go to the provider's developer settings (e.g., Slack API, GitHub Developer Settings)
- Create a new OAuth application
- Set the redirect URL to your Weavz instance's connect callback URL:
text
https://api.weavz.io/api/v1/connect/oauth-callback - Note the Client ID and Client Secret
Step 2: Register with Weavz
Open Settings
Navigate to Settings > OAuth Apps in the Weavz dashboard.
Create a new OAuth app
Click Create OAuth App and select the integration (e.g., Slack, GitHub).
Enter credentials
Paste the Client ID and Client Secret from the provider's developer portal.
Configure scopes (optional)
Enter custom scopes if you want to override the defaults. Leave blank to use the integration's default scopes.
Save
Click Save. All new connections for this integration will use your custom OAuth app.
Optional Configuration
Some OAuth providers use non-standard endpoints or require additional parameters. When registering your OAuth app in the dashboard, you can optionally configure:
| Field | Required | Description |
|---|---|---|
integrationName | Yes | The integration this OAuth app is for |
clientId | Yes | OAuth Client ID from the provider |
clientSecret | Yes | OAuth Client Secret from the provider |
authUrl | No | Custom authorization endpoint URL |
tokenUrl | No | Custom token exchange endpoint URL |
scope | No | Space-separated OAuth scopes to request |
extraParams | No | Additional parameters to include in the auth request |
Redirect URL Configuration
When creating your OAuth application with the provider, set the redirect URL to:
https://api.weavz.io/api/v1/connect/oauth-callbackFor enterprise on-premise deployments, replace api.weavz.io with your dedicated API URL. Contact sales for details.
Priority
When a custom OAuth app is registered for an integration, it takes priority over the platform's built-in OAuth credentials. This applies organization-wide — all users in your organization will use your custom OAuth app when connecting to that integration.