App Marketplace

In our Apps, we need to be able to archive/delete old conversation providers without having to create a brand new application.

Currently, developers have to set up external hosting, servers, and databases (AWS, Firebase, Vercel, etc.) to power their custom GoHighLevel apps. This creates unnecessary friction, cost, and complexity—especially for small development teams and white-labeled SaaS owners who want to build native-style integrations directly within the GoHighLevel ecosystem. Feature Request: Enable developers to host both their frontend apps and backend services natively inside GoHighLevel’s infrastructure — just like how GHL currently handles snapshots, funnels, automations, etc. This could be done through: A native “App Hosting” environment in the Developer Portal. Built-in database and API hosting capabilities (e.g., access to a GHL-managed Firestore-like or Postgres-like database). Serverless function support for backend logic (similar to Firebase Functions or AWS Lambda). Secure GHL API integrations so hosted apps can directly interact with CRM data, contacts, workflows, and automations. Why This Matters: ⚡ Speed: No need to manage deployment pipelines or servers. 💰 Cost-Effective: Eliminates third-party hosting expenses for small developers. 🔒 Security & Compliance: All data stays within GoHighLevel’s infrastructure — simplifying compliance and user data handling. 🧱 Ecosystem Growth: Makes it easier for developers to innovate and release new apps faster, enriching the GHL marketplace. ♻️ True All-in-One Platform: Extends GHL beyond marketing automation into a full no-code/low-code app platform. Summary: Let’s empower developers to build, host, and scale apps 100% natively on GHL, removing the need for any external servers or databases. This would position GoHighLevel as not just a marketing platform — but a true all-in-one SaaS creation ecosystem.

The current endpoint (/marketplace/billing/charges/has-funds) only returns a boolean for whether a wallet has any funds — it doesn't check against a specific charge amount. This breaks pre-flight cost checks for marketplace apps that incur variable, usage-based costs before billing the end user. For example, our app enriches contacts with email and phone data. If a user requests enrichment for 50 contacts, we incur a cost from our enrichment provider for every successful (positive) result — we only know the actual charge amount after the API call completes, since we're billed per successful retrieval, not per request. That means we can't charge the exact final cost to the wallet ahead of time. What we can do is calculate the maximum possible charge upfront (e.g. 50 contacts × per-contact rate, assuming a 100% success rate) and confirm the wallet can cover that worst-case amount before running the job — otherwise we risk incurring costs we can't recover from the end user. Requested change: Add a cost (or amount) query parameter to the endpoint so it checks whether the wallet balance can cover that specific charge, e.g.: GET /marketplace/billing/charges/has-funds?cost=6.35 Response: same boolean as today (true/false), but evaluated against the given cost rather than just checking for a non-zero balance. This lets apps pass in a worst-case/estimated cost and confirm funds are sufficient before incurring their own upstream costs on batch operations.

We want additional places for installable SSO secure custom pages that also have contact context. Example is the contacts panel and opportunities tab. This is like zoho and salesforce widgets. We need this to compete with these other CRMs.

We are doing marketing in Nepal and huge potential but due to the missing of payment gateway it is being difficult to execute. We request to integrate these gateway.

Feature Request: Prospecting Premium Data Visible on Pipeline Cards Currently, Prospecting Premium report data (audit scores, findings, etc.) is stored in contact custom fields but is not visible on pipeline opportunity cards. Users have to leave the pipeline view and open each individual contact record to access this data. Requested improvement: Surface key Prospecting Premium report fields directly on the pipeline card so users can assess prospect quality without leaving the pipeline view. Use case: When working a list of prospects in the "Report Generated" stage, users need to quickly see audit results to prioritize who to reach out to — without clicking into each contact one by one.

We want to be able to install a custom nav bar icon that opens a popup iframe. This would use the current SSO feature to then give us context of the account they are in. If they are viewing a contact or opportunity then we would also get that added context. This helps apps add functionality where we can open our installed apps from anywhere in the highlevel software. So this is helpful for custom support chat widgets and a variety of use cases.