4:46सारांश. Private integrations give sub-accounts a controlled way to connect custom applications and internal tools to GoHighLevel through the API. The setup involves creating a private app inside the Integrations section of sub-account settings, choosing the data scopes the app needs, and generating client credentials. Once connected, the external tool can exchange data with GoHighLevel contacts, workflows, and other features without requiring marketplace approval.
आप क्या सीखेंगे
- What private integrations are and when to use them instead of the marketplace
- How to create a private app inside sub-account settings
- How to configure OAuth scopes to limit what data a connected app can access
- How to generate and store client credentials securely
- How to verify that the connection is live and working
स्टेप
Open sub-account settings
Navigate to the sub-account where you want the integration and click Settings in the left sidebar.
Go to the Integrations section
Inside Settings, find and click Integrations. Scroll to the Private Integrations or App section depending on your account version.
Create a new private app
Click the button to create a new app. Give it a clear name that identifies the external tool it will connect to.
Select the required scopes
Choose only the API scopes your app needs, such as contacts read/write, conversations, or opportunities. Keeping scopes narrow reduces risk if credentials are ever exposed.
Generate credentials
Save the app to generate a client ID and client secret. Copy these immediately and store them securely, as the secret is shown only once.
Authorize the connection in your external tool
Paste the client ID and secret into your external application's configuration. Complete the OAuth handshake so the tool receives an access token it can use for API calls.
Test and confirm
Run a test request from your external tool, for example fetching a contact, to confirm the token works and the scopes are correct.
टिप्स
- Use a descriptive app name so you can identify it quickly if you need to revoke access later.
- Rotate credentials periodically, especially for tools with broad scopes.
- If your tool needs write access to contacts but not billing, configure only the contacts scope.
