Installing a GoHighLevel marketplace app technically takes about three minutes — click Install, authorise permissions, done. Installing it safely — at the right level, with the right scopes, tested before client data sees it — takes a bit more thought. This guide walks through the full playbook.
Before you install: the 30-second sanity check
Don’t click Install on the first app that matches your search. Run a 30-second sanity check first:
- Does an existing app already do this? If you install three apps that solve the same problem, you’ll keep paying for two of them long after you’ve picked a winner.
- Read the pricing page, not the splash page. A $19/month app with $0.05 per SMS becomes a $400 bill the first time you run a real campaign.
- Check community signal. Marketplace ratings are gameable; community upvotes from authenticated agencies (the kind we collect on this directory) are harder to manipulate.
Step 1: Open the GoHighLevel App Marketplace
Sign in to your HighLevel agency dashboard. In the left sidebar, click App Marketplace. You’ll see a searchable directory of every published app — the same data we mirror in the community directory (with extra ratings).
Step 2: Find the right app
Use the search bar or category filters to find an app that fits your job — not a category, a specific job. (See our buying framework for why this matters.) Read the listing’s description, pricing, ratings, and screenshots. Cross-check the app on this directory to see what real agencies actually say about it.
Step 3: Click Install
On the app detail page, click Install. HighLevel asks whether you want to install at the agency level or a specific sub-account:
- Agency level applies the app to every sub-account under your agency, with one combined billing line. Use this for tools every client needs (a global reporting dashboard, a Stripe integration, a default workflow library).
- Sub-account level scopes the app to a single client. Use this for niche tools only one or two clients need — that way you can charge those clients for the cost directly.
Step 4: Review the permissions screen
HighLevel shows you the scopes the app is requesting: contacts, opportunities, workflows, calendars, payments, SMS, email, etc. Read each permission carefully.
Red flag: a pure reporting app that asks for permission to send SMS, modify billing, or write to contacts. If a scope doesn’t map to the app’s stated purpose, cancel and contact the developer before continuing.
Step 5: Authorise
Click Authorise. The app is installed. For paid apps, billing begins on this step — not when you actually start using the app. If you change your mind in the next 24 hours, uninstall immediately to avoid the first invoice.
Step 6: Complete external OAuth flows (if any)
Many apps need to connect to external services like Google, Stripe, Twilio, Meta, or Zapier. Each external service has its own OAuth flow. Read the app’s documentation for the order connections need to be made — sometimes (Stripe before invoicing-related apps, Google before calendar apps) order matters.
Step 7: Test in a staging sub-account
Don’t expose a brand-new app to live client data on day one. Use a dedicated staging sub-account — fake contacts, non-routable phone numbers, dummy opportunities — for at least 48 hours. Run the app’s primary workflow end-to-end and verify nothing weird happens to your data model.
This step costs you 48 hours and saves you the support ticket-storm that follows when an app silently overwrites a custom field on a real client account.
Step 8: Document and roll out
Record the app name, install date, sub-accounts affected, and the team member responsible in your internal stack documentation (a Notion page or shared sheet works fine). This single habit pays for itself the first time an app changes pricing, breaks, or needs to be migrated — you’ll know within minutes which clients are affected.
What to do after install
Set a 30-day reminder to check whether the app is actually being used. If usage is zero or near-zero by day 30, uninstall before the second monthly invoice. Most paid apps charge based on installed status, not active use — “we’ll get around to it” mode silently bleeds your stack budget.
Common installation problems
The app installed but nothing happened
Some apps require post-install configuration (custom fields to be created, workflows to be enabled, integrations to be authorised). Check the app’s documentation for a “first run” section — most have one. If not, contact the developer’s support.
Permission denied during OAuth
Usually a Google Workspace or Meta admin policy that blocks third-party apps. Either get the workspace admin to whitelist the app or use a personal Google account for testing first.
The app charges me even though I'm not using it
Most paid apps bill on installed status, not active use. If you uninstalled and still see charges, contact the developer’s support — and double-check whether you uninstalled at the agency level or only one sub-account.
Next reading
Once your install workflow is solid, the next leverage points are choosing well (the buying framework), staying lean (the free apps roundup), and getting the right CRM extensions (our best CRM apps for 2026 list).