Skip to content
App marketplace

Marketplace Apps - Managing External Connections

Apps enable you to integrate GHL Customer Care with third-party applications. To achieve this integration, you must connect the app with the third-party…

1 min read166 words2 explained imagesUpdated Thu, 13 Feb, 2025 at 12:38 PM
View as markdownOpen in ClaudeOpen in ChatGPT
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.

Apps enable you to integrate GHL Customer Care with third-party applications. To achieve this integration, you must connect the app with the third-party application. This document explains how these connections work and are managed.

Understanding the basics

  • All connections are made at the sub-account level. So each sub-account will have a unique connection with the third-party app
  • If you're installing an app that requires external connection to a particular sub-account, the connection request will launch immediately after the installation is completed.
Understanding the basics (image 1 of 2) What this shows All connections are made at the sub-account level. What this shows Illustrates the "Understanding the basics" section of "Marketplace Apps - Managing External Connections". This screenshot appears in the "Understanding the basics" section of "Marketplace Apps - Managing External Connections". The text alongside this image reads: All connections are made at the sub-account level. So each sub-account will have a unique connection with the third-party app If you're installing an app that requires external connection to a particular sub-account, the connection request will launch immediately after the installation is completed. Immediately after, the guide continues: If you are bulk-installing an app across multiple sub-accounts, then the connection request is not automatically launched during installations. Since the connections are established at individual sub-account level, your sub-account users…. Image 1 of 2 What this coversAll connections are made at the sub-account level. So each sub-account will have a unique connection with the third-party app If you're installing an app that requires external connection to a particular sub-account, the connection request will launch immediately after the installation is completed. Next stepIf you are bulk-installing an app across multiple sub-accounts, then the connection request is not automatically launched during installations. Since the connections are established at individual sub-account level, your sub-account users must connect the app within the sub-account marketplace.
All 2 steps in this procedure
  1. All connections are made at the sub-account level. So each sub-account will have a unique connection with the third-party app
  2. If you're installing an app that requires external connection to a particular sub-account, the connection request will launch immediately after the installation is completed.
  • If you are bulk-installing an app across multiple sub-accounts, then the connection request is not automatically launched during installations. Since the connections are established at individual sub-account level, your sub-account users must connect the app within the sub-account marketplace.
Understanding the basics (image 2 of 2) What this shows If you are bulk-installing an app across multiple sub-accounts, then the connection request is not automatically launched during installations. What this shows Illustrates the "Understanding the basics" section of "Marketplace Apps - Managing External Connections". This screenshot appears in the "Understanding the basics" section of "Marketplace Apps - Managing External Connections". The text alongside this image reads: If you are bulk-installing an app across multiple sub-accounts, then the connection request is not automatically launched during installations. Since the connections are established at individual sub-account level, your sub-account users must connect the app within the sub-account marketplace. Immediately after, the guide continues: We currently support three types of authentication methods. Image 2 of 2 What this coversIf you are bulk-installing an app across multiple sub-accounts, then the connection request is not automatically launched during installations. Since the connections are established at individual sub-account level, your sub-account users must connect the app within the sub-account marketplace. Next stepWe currently support three types of authentication methods:
All 2 steps in this procedure
  1. All connections are made at the sub-account level. So each sub-account will have a unique connection with the third-party app
  2. If you're installing an app that requires external connection to a particular sub-account, the connection request will launch immediately after the installation is completed.

What authentication methods are supported?

  • We currently support three types of authentication methods:
    • OAuth - Login with third-party app and authorise the integration
    • API Keys - Copy API key from the third-party app and paste it in GHL Customer Care
    • Basic Auth - Username/Password credentials of your third party app 

Frequently asked questions

What authentication methods are supported?
We currently support three types of authentication methods: OAuth - Login with third-party app and authorise the integration API Keys - Copy API key from the third-party app and paste it in GHL Customer Care Basic Auth - Username/Password credentials of your third party app

Was this guide helpful?

Related guides

Marketplace Workflow Actions10 min read · 45 imagesMarketplace Workflow Triggers6 min read · 22 imagesAPI Security - OAuth Consent for Marketplace Apps3 min read · 2 imagesApp Marketplace- Agency Reselling for Apps with Usage-Based Pricing4 min read · 8 images