App Marketplace

Native Serverless Functions / Payload Mapping for App Marketplace Integrations
The Problem: Currently, building custom integrations (like custom triggers with Dynamic Select filters) in the App Marketplace requires returning data in a very specific format (e.g., label and value arrays). While GoHighLevel handles the OAuth connection beautifully, the marketplace lacks a native way to translate or map the raw JSON payloads coming from third-party APIs (like Google Classroom, Facebook, etc.) into the format GHL expects. This forces app creators to stand up and maintain our own external servers, AWS Lambda functions, or pay for third-party middleware (like Make.com/Zapier ) just to handle simple JSON translation. This introduces unnecessary friction, ongoing maintenance costs, and points of failure for what should be a seamless integration process. The Proposed Solution: Introduce a lightweight, native Serverless Function environment or a Visual Payload Mapper directly within the App Marketplace builder. When configuring an "Options URL" for a dynamic dropdown, allow creators to write a simple snippet of Node.js code natively within GHL to fetch the 3rd party data, map it to label/value, and return it. Alternatively, provide a visual JSON mapper that lets us select the arrays from the 3rd-party endpoint and assign them to GHL's expected fields. Why This Benefits App Creators: Drastically Lowers Barrier to Entry: Creators can build fully functional, dynamic apps without needing full-stack development skills or cloud hosting accounts. Faster Development Cycles: Eliminating the need to deploy and manage external middleware means apps can be built and pushed live in a fraction of the time. Fewer Points of Failure: Keeps the entire integration pipeline under one roof, reducing bugs caused by third-party server timeouts. Why This Benefits GoHighLevel (The ROI): Explosive Marketplace Growth: By removing the "external server" bottleneck, you will empower thousands of non-developer agency owners to build and publish custom apps, rapidly expanding the GHL ecosystem. New Monetization Opportunity: We (and many other creators) would absolutely be willing to pay a premium subscription or usage-based fee for native compute power/serverless execution directly inside GHL. This could become a highly profitable add-on for the marketplace. Ecosystem Lock-in: It keeps developers building inside GoHighLevel rather than relying on external tools like Zapier or Make, cementing GHL as the ultimate, all-in-one platform. We would love to see this implemented and are ready to support it (and pay for it) if it becomes available!
1
Enhance "Check if account has sufficient funds" endpoint to check against a specific charge amount
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.
1
·
under review
Load More
→