Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Go High Level

Go High Level artwork

How to Manage Marketplace App Connections in GoHighLevel

Apr 28, 202618 minAudio
ShareXLinkedInFacebookWhatsAppEmail

🚀 Start your FREE 30-day GoHighLevel trial: https://globalhighlevel.com/trial In this episode, we dive into managing external connections through GoHighLevel's marketplace apps. Learn how to seamlessly integrate third-party applications with your sub-accounts and streamline your agency's workflow automation. In this episode you'll learn: • How marketplace app connections work at the sub-account level • When connection requests launch automatically after app installation • Best practices for bulk-installing apps across multiple sub-accounts • How to manage and troubleshoot external integrations in GoHighLevel Ready to try GoHighLevel yourself? The link above gets you a FREE 30-day trial - double the standard 14-day trial. See why thousands of agencies run their entire business on one platform.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show.

So if you're just, you know, fixing a squeaky hinge around the house, a basic off-the-shelf toolkit does the job perfectly fine. Right, a little red toolbox, maybe some WD40 and you're good. Exactly. But when you transition to uh building a 50-story skyscraper, suddenly that little toolbox isn't going to cut it at all. No, I mean, you need tower cranes, you need specialized laser levels. Enterprise grade machinery, basically. Yeah. Your tools have to scale with the sheer ambition of your project. And uh before we start unpacking the heavy machinery on today's deep dive, I want to make sure you actually have access to the crane, so to speak. Which is pretty important. Yeah, totally. So if you are listening to this right now, joining us for this conversation, you can get a free 30-day GoHighLevel trial. Which is huge. It is. That is actually double the standard trial length, and the link is waiting for you right down in the show notes. So go grab that because we are about to get into the absolute architecture of scaling your digital empire. And it really does change the entire dynamic of how you operate. Like going from managing just a handful of local businesses to running a massive marketing agency, I mean, the stakes for precision engineering are just significantly higher. Because a single inefficiency gets multiplied by what, 50 or 100 clients? Exactly, it cascades. So our mission today is to pull apart the mechanics of the high-level support portal documentation. Specifically looking at marketplace apps and external authentication. Right, the real nuts and bolts. Yeah, we're looking at how digital marketing agency owners can actually deploy custom tools across client sub-accounts. And more importantly, how to, you know, actually secure those integrations. Because security is everything at that scale. Oh, 100%. So we are skipping the basic overviews today and going straight into the how and the why of the platform's architecture. I love it. And just to set the context here, the app marketplace inside high-level, um, it's not a wild west scenario. Right. It's not just anyone throwing code up there. No, not at all. You can't just have any random developer uploading a piece of software. It is a highly scrutinized ecosystem. Like every application goes through this really rigorous evaluation by their internal developers. So it's vetted. Very heavily vetted. The entire infrastructure is designed to turn a standard agency account into this uh, deeply customized software powerhouse. Which honestly makes sense of the first major gatekeeping rule I notice when going through the docs, because this ecosystem is definitely not open to everyone. Right, you have to have the right tier. Yeah, to even access the agency level at marketplace, you have to be holding a specific VIP pass, namely the freelancer or the agency Pro plans. Yep, that's the threshold. It kind of feels like, um, an exclusive high-end hardware store for digital architects. Like you have to flash your badge at the door. That's actually a great analogy. And the intent behind gating that access is purely about scale. I mean, those specific plans are engineered for agency owners who are actively managing large fleets of clients. So they need the heavy machinery. Exactly. The tools inside this marketplace are built to modify the platform at a macro level, but, you know, as you can probably imagine, dropping an agency owner into this massive repository of enterprise tools, it can easily lead to severe decision fatigue. Oh, absolutely. You go in there looking for like a simple calendar integration, and then three hours later, you're staring at AI voice synthesizers and predictive analytics tools. And you've completely forgotten what you even logged in to do. Yeah. My shopping cart is full of stuff I don't need. So I assume the platform has some way to organize this chaos, right? Probably by grouping tools based on their core function rather than just throwing them into one giant searchable list. They do. Yeah. They utilize these curated lists called app collections. So instead of just endless scrolling, you dive into specialized hubs. Okay, that makes sense. Like what kind of hubs? So for instance, there is the Custom Experience Hub. And this is specifically for agencies that want to heavily modify the user interface, you know, using custom JavaScript and CSS scripts. Oh, wow. So like really deep customization. Yeah, exactly. If you want to completely white label the look and feel of the software for your clients, that is where you go. And then you have the Workflow Automation Hub, which is for specialized actions and triggers, and, uh, the Conversation Hub for integrating third-party messaging systems. Okay, treating it like a categorized library rather than a messy garage sale, definitely saves a massive amount of time. But, um, when I'm looking at an app in one of these hubs, say a third-party messaging integration, I still need to know what it's actually doing behind the scenes. Right, you need to know what you're letting into your house. Exactly. Like, if I install this, is it going to start reading all my client's private contacts, or randomly modifying their calendars? Well, total visibility is built right into the listing page. Before you ever even hit the install button, the permission detail section breaks down the exact scope of access that specific application is requesting. Oh, okay. So it's right there in plain English. Yeah, it functions as a security manifest. You can see definitively, you know, if it requires read access to contacts or write access to calendars. And there's a pretty critical operational distinction to make here too, regarding who handles the troubleshooting. Right, because if something breaks, who do I yell at? Exactly. HighLevel natively supports its own applications, obviously, but if you inject a third-party app into your ecosystem, the support comes directly from that external provider. I mean, that makes total sense. You wouldn't call Apple if your Netflix app suddenly stopped loading on your iPad. Right, you'd call Netflix. So the baseline strategy here for an agency owner is uh, utilize the hubs to bypass the clutter, rigorously check the permission details so you aren't accidentally giving an app the keys to the kingdom. Very important. Yeah, and know exactly who to contact if a specific tool breaks. Spot on. But, you know, finding and vetting the tool is really just the starting line. The true test of an agency's operational capacity is how systematically they can deploy that tool across their entire client base. Right, the actual logistics of scale. Because installing a custom dashboard for one client, that takes what, five minutes? If that, yeah. But pushing it to 200 sub-accounts at the exact same time is a completely different beast. So how does the platform handle that? It handles it through different distribution types. So the first is an agency app, which is exclusive to the macro level. Your clients, meaning the sub-accounts, they cannot install or even see these. Okay, so they're totally hidden. Totally hidden. They are purely for your internal agency management. But then, we have the Agency and Sub-Account distribution model. Okay, that sounds like where the heavy lifting happens. It absolutely is. These apps are initiated at your agency level, but you have the power to push them down to specific sub-accounts, or just blast them out to all of your clients simultaneously. Okay, wait, let's address the massive operational risk here though. Because I'm thinking about this, and many of these tools in the marketplace are premium paid apps, right? Right, they have monthly fees. So if I am an agency owner attempting to push a paid app down to 50 clients all at once, I am immediately sweating about the billing mechanics. Like, if an app processes payments within the HighLevel platform, who is actually getting charged? That's a great question. The cost of the application is charged directly to each individual sub-account's card on file. Oh yeah. The platform literally routes the billing down to the specific client utilizing the tool. Hold on. So if I'm pushing a paid app to 50 clients to, you know, upgrade their systems, and I know for a fact that 10 of them have expired credit cards, or they just never put one on file, am I looking at a total system crash? You're worried it'll break the whole batch. Yeah. Because I've seen mass deployments in other softwares just fail completely over one bad card, and it forces you to start the entire process over from scratch. Right, that is the exact nightmare scenario operations managers fear. But the architecture actually handles what we can call the missing card scenario with a really graceful failure mechanism. Oh, thank goodness. How does it work? Well, if you bulk install to 50 sub-accounts, and 10 of them lack valid payment details, the system doesn't freeze. It just elegantly processes the installation for the 40 eligible accounts, and then simply skips the remaining 10. Oh, wow. That isolates the friction entirely. Exactly. You don't lose the momentum of the rollout. It keeps the whole deployment moving. And the best part is, it tracks the failures. So it tells you who messed up. Right. So once you reach out to those 10 specific clients and have them, uh, update their billing profiles, you can navigate back and retry the installation process specifically for those previously ineligible accounts. Without disrupting the 40 that are already up and running. Exactly, without touching them at all. That is incredibly smart. I mean, conducting a card-on-file audit of your sub-accounts before attempting a mass rollout of a new paid app seems like a mandatory standard operating procedure anyway. Oh, absolutely. You should definitely be doing that. It prevents the headache entirely? Yeah. But let's say the rollout goes smoothly, right? The app is paid for, and it's physically sitting in the client's sub-account. From what I read in the documentation, the job still isn't done. The tool still has to actually shake hands with the external third-party software. Yes. And this is a vital distinction between just installing an app and actively connecting it, because all external connections are made strictly at the sub-account level. Because it's their specific data. Exactly. Every client has their own unique data, their own unique login credentials for whatever third-party service you are integrating. HighLevel can't log in for them. So it's like delivering a fancy new smart TV to 50 different hotel rooms. As the agency owner, I use the bulk install feature to, you know, drop off the TV in each room. Right. But the hotel guests still have to physically walk into their room, turn the TV on, and log into their own personal Netflix accounts. Mhm. I can't do that for them because I obviously don't have their personal passwords. That analogy perfectly illustrates the limitation of a bulk deployment. Like, if you install an app for just one single sub-account, the system recognizes you are focused on that specific client, and the connection request actually auto-launches immediately. Oh, so it pops right up. Yeah, it prompts you right then and there to authorize the handshake. But if I drop off 50 TVs at once, my browser obviously can't simultaneously launch 50 different authorization screens. Right, it's technically impossible. So in a bulk install scenario, the connection request does not auto-launch. The application is successfully delivered, but it just remains dormant. It just sits there. Exactly. The sub-account users, meaning your clients, they must log into their own workspace, navigate to their sub-account marketplace, and manually initiate the connection themselves. See, if an agency owner doesn't understand that operational gap, they are going to assume they just delivered this massive technological upgrade. And meanwhile, their clients are going to see a dead app sitting on their dashboard doing absolutely nothing. And then the complaints start rolling in. Yeah. So the takeaway is that technology can't replace proactive communication. A bulk install really must be paired with clear step-by-step instructions sent to the clients on how to log in and authorize that final connection. The human process bridges the final technical gap. It always does. Now, once the client actually clicks that authorize button, we need to look under the hood at how the platform actually handles that external connection. Right, the security layer. Because when sensitive client data, you know, customer lists, financial transactions, lead flow, when that is moving across the internet, how does the system ensure that handshake is secure? And this is where we have to look at the three supported authentication methods outlined in the docs. The most basic one is the traditional API key. You just copy a long string of characters from the third-party app and paste it in. Yep, very standard. Then there is basic off, which is your standard username and password. Interestingly though, the platform actually restricts basic off to a maximum of three fields. So like, username, password, and maybe a company ID, but nothing more. Yeah. And that restriction on basic off is a deliberate security measure. It's designed to prevent overly complex or bloated credential passing that could potentially be vulnerable. Makes sense. Keep it simple, keep it secure. Exactly. And regarding API keys, while they are extremely common, they are essentially a master key to a house. Oh, right. Because they don't expire. Exactly. They just stay active. If someone intercepts an API key, they have permanent access to that data pipeline until you manually go in and revoke it. Which brings us to the third, and really the most robust method, Oath 2.0. Yeah. Oath 2.0 is the modern industry standard. It's less like giving someone the master key to your house and more like giving them a temporary hotel key card. I like that. You know, it only opens specific doors, and it automatically expires at checkout. HighLevel supports the authorization code grant type for this, but, uh, the layer that really caught my attention in the documentation is their implementation of something called PKCE. Ah, yes. PKCE, or Proof Key for Code Exchange. This is where the architecture gets incredibly sophisticated. Okay, I can literally hear agency owners listening right now, asking why they need to care about developer level jargon like PKCE. Like if I just build sales funnels and run ad campaigns, why does the underlying token exchange math matter to me? I get that pushback all the time. But it matters because your enterprise clients care deeply about data liability. When you are moving their proprietary data, you are carrying their trust. And their liability. Exactly. If a bad actor intercepts a standard authorization code during that initial handshake over the internet, they could theoretically hijack the connection and redirect the data flow entirely. Which is a disaster. Total disaster. But PKCE prevents this by generating a mathematically unique code verifier and code challenge for every single authorization request. So it's kind of like a secret cryptographic handshake that dynamically changes every single time the two servers talk to each other. Right. Meaning, even if someone intercepts the code in transit, they don't know the secondary secret handshake, so the door stays locked. The interception becomes entirely useless. The third-party server will just reject the connection because the attacker can't produce the verifier. Wow. And understanding that this grade of mathematical security is baked into the platform, it allows you to confidently sit in a boardroom with an enterprise client and guarantee that their data pipelines are hardened against interception attacks. Yeah, it stops being just developer jargon and becomes a massive selling point for your agency. It transitions from a technical feature to real piece of mind for the client. Now, once that secure connection is established, there's another setting under OAuth 2.0 that seems incredibly critical for long-term stability. And that's the auto-refresh token. Right, because without this, everything just stops. Literally. This is the mechanism that prevents your agency from grinding to a halt on a Saturday night. Because Oath utilizes those temporary hotel key cards, you know, access tokens, they inherently have a lifespan. They expire usually after a few hours or maybe days for security purposes. And if you don't have an automated way to basically go back to the front desk and get a new key card, the client's integration simply breaks. Just shatters. Yeah, the leads stop flowing into their CRM, their automated emails fail, and the client picks up the phone to demand answers on a weekend. Right. If the auto-refresh token is disabled, the connection just dies upon expiration. The user is forced to manually re-authenticate all over again. But by enabling it, the platform handles the negotiation for new token pairs entirely in the background. Your workflows just continue uninterrupted. And what's really impressive to me is how the platform actually optimizes the timing of that refresh. Yeah. It isn't just, you know, mindlessly pinging the third-party server every five minutes to check if the token is still valid. Right, which would burn through API rate limits incredibly fast. Exactly. Yeah, the architecture actually utilizes a just-in-time refresh mechanism. HighLevel only checks the validity of the token when a workflow containing custom actions or triggers is actively about to execute. Oh, that's clever. Isn't it? In the millisecond before the action fires, it verifies the token, refreshes it right then if necessary, and then processes the data. It saves bandwidth and ensures absolute reliability right at the critical moment of execution. I mean, if we pull all of these structural pieces together from the deep dive today, we are looking at a massive evolution in agency capability. We really are. We started by unlocking the marketplace with the freelancer or agency pro pass, which protects the whole ecosystem. Bypassing decision fatigue by utilizing curated app collections to find specific UI and automation tools. Right. And then we navigated the friction of mass deployment, relying on the graceful failure of that missing card scenario to just keep the rollouts moving forward. We highlighted the operational necessity of having clients manually authorize those bulk installed apps. And finally, we unpacked the deep architecture of OAuth 2.0, PKCE, and that just-in-time token refreshing that ensures those connections are absolutely bulletproof. It is a profound amount of technological leverage placed directly into the hands of an agency owner. Like truly enterprise-level stuff. It is. And honestly, it prompts a fascinating re-evaluation of your role in the market. How so? Well, when you possess the ability to deploy heavily secured, deeply integrated infrastructure, and you can push custom experience hubs with bespoke code directly into hundreds of sub-accounts all at once, at what point do you stop being a traditional marketing service provider and start functioning as a bespoke software company in your own right? Wow. That is the question. Because you aren't just running their Facebook ads anymore. You are architecting their entire operational software stack. You are literally building the skyscraper. Exactly. That is a massive paradigm shift. Every digital marketing agency owner should be thinking about. Yeah. And uh, if you want to start building that skyscraper, today, you can put all of this architecture to the test right now. That free 30-day GoHighLevel trial, which again is double the standard length, is waiting for you. Go grab it. Seriously. Click the link down in the show notes, get into the platform, and just see what you can build. Thanks for diving deep with us, and we will catch you on the next one.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Stop Chasing Leads: Auto Follow-Up in Conversation AI

    Oct 6, 202626 minAudio

    Your AI bot can now automatically follow up with inactive contacts - no manual work required. Learn how HighLevel's Conversation AI detects drop-offs, schedules smart reminders, and closes deals on autopilot. Watch this...

    Credit the people on this episode

  2. Knowledge Base Triggers: Control Your Conversation AI Responses

    Oct 6, 202617 minAudio

    Stop letting AI guess when to show offers and pricing. Learn how GoHighLevel's Knowledge Base Triggers deliver the right content at the exact moment your prospects need it - driving more conversions and eliminating...

    Credit the people on this episode

  3. Conversation AI on Mobile: Reply to Customers Instantly (No Desktop Needed)

    Oct 6, 202617 minAudio

    Manage customer conversations from your phone with Conversation AI in the HighLevel mobile app. Learn how to use Autopilot Mode, Suggestive Mode, and control your AI assistant on-the-go across WhatsApp, Facebook,...

    Credit the people on this episode

  4. Voice AI Agent Transfer: Route Calls Without Dropping Them

    Oct 6, 202623 minAudio

    Learn how GoHighLevel's Voice AI Agent Transfer hands off live calls between specialized agents seamlessly - no dial transfers, no restarts. Discover how to route callers to sales, support, billing, or language-specific...

    Credit the people on this episode

  5. Sell Your AI Agents: GoHighLevel Marketplace Launch Guide

    Oct 6, 202620 minAudio

    Turn your Conversation AI and Voice AI templates into revenue streams. Learn how to package, list, and sell your agents on the GoHighLevel Marketplace - complete with workflows, automations, and knowledge bases...

    Credit the people on this episode