How to Use Private Integrations in GoHighLevel
If you manage multiple tools like ClickUp and want deeper automation inside your CRM, learning how private integrations work in GoHighLevel is essential. This guide walks you step by step through requesting access, building, testing, and sharing private integrations so you can safely extend your account without exposing your apps publicly.
Private integrations let you connect GoHighLevel to your own apps or client solutions using OAuth, while keeping them hidden from the public integrations marketplace. They are ideal for agencies, developers, and SaaS owners who need secure, controlled access to CRM data.
What Is a Private Integration in GoHighLevel?
A private integration in GoHighLevel is an OAuth-based connection that is visible only to you and the sub-accounts you explicitly choose. It does not appear in the public integration list and can only be installed through a direct installation URL.
With a private integration, you can:
- Access GoHighLevel APIs using OAuth tokens.
- Specify exactly which scopes and permissions your app needs.
- Share the integration only with selected sub-accounts or businesses.
- Test, iterate, and control updates without a public release.
Requirements Before You Start in GoHighLevel
Before creating a private integration in GoHighLevel, you must meet these conditions:
- Your account must be enabled for integrations.
- You need admin or owner-level access for the agency account.
- You must understand which APIs and scopes your app will require.
- You should be able to provide accurate app details, such as name, logo, and redirect URLs.
Once these requirements are ready, you can request a new integration from the integrations area in your agency view.
How to Request a Private Integration in GoHighLevel
Follow these steps to request and configure a private integration in GoHighLevel:
Step 1: Submit a New Integration Request
- Go to your agency account and open the integrations section.
- Look for the option to request or create a new integration.
- Select the Private Integration option when prompted.
- Fill in the required information, including:
- App name and description
- App logo or icon
- Contact details
- Redirect URL for OAuth
Be clear and precise, because this data is used to generate the OAuth configuration for your GoHighLevel integration.
Step 2: Choose Your GoHighLevel Scopes
Scopes define what your private integration can see and do inside GoHighLevel. When configuring your integration, you will need to select specific scopes such as:
- Lead and contact management
- Pipelines and opportunities
- Calendars and appointments
- Conversations and messaging
- Workflows and automation
Only select the scopes that are absolutely required for your use case. The more precise you are, the safer and more compliant your integration will be.
Step 3: Wait for Integration Review and Approval
After submission, the GoHighLevel team reviews your private integration request. They verify:
- The accuracy of the app details.
- The validity of the redirect URLs.
- The appropriateness of requested scopes.
If any changes are required, you may be asked to update your request. Once everything is correct, the integration will be approved and you will receive the client ID and client secret required for your OAuth flow.
Setting Up OAuth for Your GoHighLevel Private Integration
When your integration is approved, you can configure the OAuth flow in your app or backend.
Step 4: Configure OAuth Redirect and Authorization
- Use the provided client ID and client secret from GoHighLevel.
- Implement the OAuth 2.0 authorization code flow in your application.
- Make sure the redirect URL in your app exactly matches the URL you submitted.
- Handle the authorization code and exchange it for access and refresh tokens through the GoHighLevel token endpoint.
Store tokens securely and respect token expiration and refresh rules when calling the APIs.
Step 5: Test the Private Integration in a Sub-Account
Before sharing your private integration widely, test it in one or more sub-accounts:
- Generate or copy the installation URL for the integration inside GoHighLevel.
- Open a test sub-account where you have admin access.
- Use the installation URL to install the private integration.
- Complete the OAuth authorization step and confirm the correct scopes.
- Trigger actions in your app to confirm data flows and permissions are correct.
Fix any errors or misconfigured scopes before rolling out the integration more broadly.
Whitelisting and Sharing Your GoHighLevel Private Integration
Private integrations can be shared only with specific accounts. They do not appear for general users, which makes them ideal for controlled deployment.
Step 6: Whitelist Sub-Accounts
To let a client or another internal business unit install your private integration, you must whitelist their sub-account inside GoHighLevel.
- Go to your integration settings in your agency account.
- Locate the private integration you created.
- Find the whitelisting or access control section.
- Add the specific sub-accounts or business IDs you want to grant access to.
Only the whitelisted sub-accounts will be able to install and use the integration via the provided installation URL.
Step 7: Share the Installation URL
After whitelisting target accounts:
- Copy the private integration installation URL from your GoHighLevel integration settings.
- Send it securely to the users or clients who need to install the app.
- Provide short instructions on how to authorize and complete the connection.
Because it is private, the only way to install this integration is through that URL and only for approved sub-accounts.
Managing and Updating Private GoHighLevel Integrations
Once your private integration is live, you may need to adjust settings or scopes as your product evolves.
Step 8: Edit Settings and Scopes
From the integration management area in GoHighLevel, you can:
- Update the app name, icon, or description.
- Modify redirect URLs if your infrastructure changes.
- Request additional scopes if your integration needs new permissions.
Scope changes may require another review, so plan ahead and request only what is necessary.
Step 9: Revoke or Disable a Private Integration
If a private integration is no longer needed or you want to stop access for certain users:
- Revoke tokens for specific sub-accounts.
- Remove sub-accounts from the whitelist.
- Disable or delete the integration from your agency account.
Once disabled, users will no longer be able to authenticate or call GoHighLevel APIs through that integration.
Troubleshooting GoHighLevel Private Integrations
Common issues with private integrations typically involve OAuth or permissions. When something does not work as expected:
- Check that the redirect URL exactly matches the URL in your GoHighLevel settings.
- Confirm that the correct scopes were granted during authorization.
- Verify that the sub-account has been whitelisted.
- Review your token handling logic for expiration and refresh errors.
You can also review the official help documentation for more details and visual examples at this GoHighLevel private integrations article.
Next Steps for Scaling GoHighLevel Integrations
Once you have mastered private integrations, you can use them as the backbone of advanced automations, internal tools, or white-labeled SaaS built on top of GoHighLevel. Consider:
- Connecting your CRM data with analytics dashboards.
- Syncing leads and opportunities to custom back-office systems.
- Building specialized client portals powered by the GoHighLevel API.
If you need strategic help designing scalable automation and integration architectures, you can explore consulting services at Consultevo for expert guidance.
By following these steps and best practices, you can reliably create, test, and manage private integrations inside GoHighLevel while keeping full control over who can access and install your apps.
Need Help With ClickUp?
If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.
“`