Subscribe
Share
Share
Embed
Welcome to our podcast, where we dive into everything Go High Level—from mastering the basics to tackling the most complex tasks. I use GHL daily in my business and rely on Google NotebookLM to stay ahead of the curve, keeping up with all the latest GHL features, tools, and innovations. This podcast is powered by AI, fueled by the research and insights I personally curate to bring you the most valuable and up-to-date content.
Copy this link for a free trial of Go High Level - https://www.gohighlevel.com/highlevel-bootcamp?fp_ref=amplifi-technologies12
Imagine a car rolls off a dealership lot and instantly like without a single human click the assigned dealer gets a text. Yeah, the finance team gets an updated spreadsheet, the inventory adjusts. Exactly. And the buyer's old lead nurture emails just terminated immediately. Right, which used to take, you know, this incredibly fragile web of expensive third-party software. And constant babysitting. But not anymore. We are taking a deep dive today into exactly how you can build this natively. But, uh, before we get into the mechanics of all that, I have something massive for you listening right now. Oh, the extended trial, right? Yes. Yeah. Usually, when you want to test drive a platform's new features, you get what? A quick two weeks to figure it out. Well, right now, you can get a completely free 30-day Go High Level trial, which is double the standard trial length. Double. It gives you a full month to get under the hood, build out the complex workflows we're about to discuss, and actually see the results for yourself. That link is waiting for you right now in the show notes below, so do not miss out. And having that full month is just is critical, especially given the sheer scale of the architectural changes we're looking at today. Oh, 100% because today's mission we're exploring Go High Level's new custom object and company-based workflow actions and triggers. Yeah, it's a bit of a mouthful, but it is huge. It really is. And if you are a digital marketing agency owner, we are laser focused on how this actually shifts your day-to-day operations. Like how these tools allow you to scale your client's businesses without just adding more manual busywork to your plate. Right. And to understand why this is such a massive shift, we kind of have to look at the limitations agencies have been hitting their heads against for years. The old way of doing things. Exactly. Previously, automations were almost entirely tied to a single record. Um, the contact. So if John Doe filled out a form, you built an automation around John Doe. Right, but businesses don't just process isolated people. No, they process complex data, inventory, you know, physical assets. Yeah. Like if you were managing a real estate client or a car dealership, you had to perform these ridiculous workarounds and an agency would literally have to create a dummy contact record for like a 2018 Toyota Camry. Yeah. Give it a fake email address like Camry@dealership.com. Yes. Just so they could apply a tag to it and fire off an internal notification. I mean, it was incredibly fragile and it just cluttered up the database. It was an absolute nightmare for pipeline hygiene. But now, Go High Level has introduced data aware relationship gridded automation. Which changes everything. It really does. It works across contacts, companies, and most importantly, custom objects. So, homes, cars, pets, support tickets, whatever central asset your client's business revolves around. So, the system now recognizes the actual object itself. Exactly. You have specific triggers now like home created or home changed. Let's pause on that because the old way of thinking, it was basically like a single lane highway. Every single automation, every tag, had to travel down that one contact record lane. Which obviously caused massive traffic jams. Right. But this new update feels more like a complex transit hub. You know, you have trains, buses, and planes contacts, companies, custom objects, all arriving on their own independent schedules. And the workflow engine is essentially acting as the air traffic controller, coordinating them all simultaneously. It's like moving from checkers to 3D chess. You make one move and it impacts interconnected pieces across different levels all at once. That is a brilliant way to visualize it. You aren't forcing the airplane to drive in the car lane anymore. Yeah. And the immediate actual impact for an agency owner is that you can build distinct, professional operational pipelines for a client's specific inventory. So, if a specific car status changes in the system, that event alone sets the gears in motion. You don't need a contact to do something first. Precisely. But if you're tracking these physical assets independently, the next, uh, immediate problem an agency faces is how to notify the right human beings without spamming the whole company. Right. If the car changes status, how does the system actually know who is attached to that specific car to tell them about it? That brings us to the new cross-object workflow actions. And the engine driving this is something called association labels. Okay. So, walk me through the mechanics of that. I have a car, right? It's just been detailed, and its status changes to ready for sale. How do I target the right person? Well, when you set up the database initially, you create relationships using labels. So, John the salesman is linked to that specific car with the association label of assigned dealer. Okay, so the label is the key. Exactly. When the car's status changes, the workflow looks at the car, scans for anyone holding that assigned dealer label, and automatically pulls them into a dealer notification workflow. Wow. So, the car changes status and the assigned dealer just gets pinged instantly. Instantly, yeah. But let's play devil's advocate for a second here. Say I'm an agency owner building this out and a property sells, I might want to trigger downstream actions for multiple people connected to that house. Yeah, that makes total sense. Like I want to unenroll the buyer from the active marketing list, but I also want to unenroll the co-signer. Can I just like lump all those labels together in one single action block to save time? Uh, no, you cannot. And honestly, you really shouldn't want to. Wait, really? Why restrict it like that? It seems like it just adds more steps to the workflow builder. I get that, but it comes down to preventing database chaos. When you're coordinating multi-tiered data, the system needs absolute mathematical clarity on exactly which relationship it's acting on. Oh, so if it breaks, you know exactly why. Exactly. If it fails or hits an error, you need to know precisely which label caused the issue. So if you want to target the buyer and the co-signer, you simply add an add associated records or remove associated records block for the buyer. And then just add a second block right below it for the co-signer. Right. It takes maybe five extra seconds to build, but it guarantees your logic is bulletproof. That makes a lot of sense. It forces you to be intentional. And you mentioned the remove action there, which I imagine is just as vital. Absolutely. The remove associated records from workflow action. It unenrolls related records the second conditions change. So if a real estate agency has a property custom object and it gets marked as sold. This action pulls the associated buyers out of the active listings workflow immediately. Which solves a massive headache for agencies. I mean, there is literally nothing worse than that embarrassing moment where a client's lead gets an automated text pitching them a house they just bought yesterday. Or a car that was just sold to someone else. By using these cross-object actions, agencies are essentially selling peace of mind. You're ensuring the client's messaging always perfectly matches the real-world status of their physical inventory. Precisely. It's about perfecting that pipeline hygiene. All right. So, we know how to push and pull records around when they are already linked up in the system. The car knows who the dealer is, the system knows the association label. Right. But what happens when the train arrives from a completely different city? Like let's say the data comes from an outside source. Like a third-party lead vendor. Yeah, or an external billing system and the records aren't explicitly connected in Go High Level yet. This is where things get highly technical but incredibly powerful. You have to use the find object record or find company action. So it goes looking for them. Exactly. It allows you to locate an existing record in your database using a record ID, an external ID, or field-based filters, all without needing a prior association. And this ties directly into dynamic inbound webhooks, right? Yes. And this is arguably the most disruptive part of the update for agency operations. You can pass dynamic values straight from an inbound webhook directly into the find action. Let's translate this because reading webhook payloads on audio can get a little dense. Good idea. Imagine a webhook sends a tiny digital envelope to your Go High Level system, and inside that envelope is just a single piece of paper with a domain name on it. Let's say acme.com. Right, acme.com. There's no name, no phone number, no associated contact, just the domain. That is a perfect analogy. Really? So, the workflow catches that envelope. It takes the piece of paper and it hands it to the find action. And then what? The find action searches your entire database for any company record that matches acme.com. When it finds it, it instantly enrolls that specific company into the next step of the workflow. It's essentially acting like a digital bounty hunter. You hand it a description of the target, the domain name. It kicks open the database stores, hunts down the exact match based on that single clue, and brings them back. Brings them right back to trigger whatever happens next. And like any good bounty hunter, it has built-in protocols for different scenarios using automatic branching logic. Oh, so what happens if it doesn't find them? The workflow immediately splits into two paths: record found and record not found. So if it comes back empty-handed, the system doesn't just crash. That's a relief. Right. You can route it down the not found path, automatically create a new record from scratch, or, you know, fire a Slack message to a human team member to investigate. But wait, what if the bounty hunter is too successful? Like, what if it searches the database for a custom field and finds three different records that all match the description? That's a great question. How does the workflow know which one to grab? Yeah, exactly. Well, the system gives you three specific ways to handle multiple matches. You can configure the find action to select earliest. Which means it proceeds with the oldest matching record in your database. Correct. Or you can select latest, which grabs the most recently created record. Both of those options funnel you down to a single definitive match. Okay, and the third option? You can choose all. If you select all, the workflow takes every single matching record it found and pushes all of them down the downstream paths simultaneously. That is immense control. And if you are an agency owner, the application here is totally clear. You are eliminating Zapier bills. Oh, absolutely. Before this, if you wanted to take a webhook from an external lead vendor, look up a company in your CRM and update a custom object, you were paying a premium subscription to a third-party integrator just to route the data. You were paying for the software and you're introducing an external point of failure. Like if the integrator went down, your client's pipeline froze. Exactly. Now, you can directly integrate external lead generation systems, billing platforms, or complex external inventory trackers straight into Go High Level natively. You save the agency money, you save the client money, and there are just fewer moving parts that can break. It's a win all around. Okay, so to truly grasp the weight of this entire update, we need to tie all these concepts together into one complete life cycle. Let's walk through the real estate use case that was detailed in the source materials. This case study is the perfect blueprint for how an agency should be thinking about their client's operations. Just to set the stage for us. We start with a real estate agency using a custom object called Home. The trigger for the entire architecture is an object changed event. So something on the home object gets updated. Specifically, the field for home status is updated from under contract to closed. Okay, the moment the status flips, what happens next? Well, the workflow fires a sequence of distinct actions. First, it handles the personnel. It uses the association label to find the specific agent linked to that sold property and updates their record. Like maybe it increments their total sold tally for the quarter or triggers an internal bonus notification. Exactly. So, that handles the internal team. Then, it handles the external reporting. Oh, so. It uses the native Google Sheets integration to add a new row to a centralized ledger, logging all the financial details of the sale. Which clients absolutely love. I mean, an agency that provides a perfectly clean, auto-updating spreadsheet without the client having to manually enter data is an agency that does not get fired. Exactly right. And finally, the third action focuses on database hygiene. The workflow automatically clears out specific custom fields on the home object. Just wiping the slate clean. Yes, it wipes the temporary viewing notes and internal comments fields, which are completely obsolete now that the home is sold. That is incredibly elegant. In one automated sweep, triggered just by changing a status to closed, you've managed the sales staff, generated external reports, and cleaned the database for the next life cycle. And the sources list out a massive toolkit of other internal actions you can apply to these custom objects. The capabilities have expanded drastically. You aren't just limited to updating fields. No, you have if/else branching, date and time formatters, math operations. But instead of just reading off the feature list, let's look at how an agency actually applies these. Take array functions, for example. Oh, that's a great one. Usually if you're dealing with an array of data, like a list of five different property viewings a buyer attended, you need a developer to parse that data. Right. It gets complicated fast. But now an agency can use the native array function block to take that list, format it into a clean, readable text block, and drop it right into a follow-up email entirely visually. Or consider the workflow AI integration. You can pass the details of the custom object, say the make, model, and specific trim of a car, directly into a GPP prompt inside the workflow. And use OpenAI to generate a highly personalized, context-aware congratulatory SMS and send it to the buyer. You're building a full-fledged enterprise logic engine right inside the CRM. It's extremely powerful. But let me ask you a setup question because I know agency owners are going to run into this. Sure. What is it? Say I am in the trenches, I'm building this massive real estate workflow. I have my triggers, I have my find actions, my AI blocks, and right in the middle of building it, I realize I need a brand new custom object to track something like, uh, closing gifts. Okay. I see where you're going. Can I just hit a button and create that new custom object on the fly inside the workflow builder? I know exactly how convenient that would be, but no. Ah, really? Yeah, the system requires rigid structure. You must create the custom object and explicitly define all of its properties and fields in the database settings before it can be referenced in any workflow trigger or action. So you have to pour the concrete foundation before you can start running the plumbing. Precisely. If you were allowed to invent objects mid-workflow, you would inevitably end up with broken data associations, duplicate fields, and just a severely degraded CRM. That makes sense. The workflow engine needs to know the exact parameters it's allowed to interact with before it starts moving data at scale. Measure twice, cut once. Exactly. So, bringing this all together for you, the agency owner listening, what we are really talking about is a shift in the service you offer. A huge shift. By utilizing these multi-step actions, replacing Zapier with native find actions, and pushing data seamlessly to external webhooks or Google Sheets, you are offering automated database management as a massive value-add. You aren't just the person running their Facebook ads anymore. No, you are architecting the central nervous system of their entire business. And when you do that, you transition from being an easily replaceable marketing expense to being structurally indispensable. Indispensable. Let's summarize the ground we have covered today. We explored the massive shift from single contact automations to relationship-based custom object workflows. We looked at how you can trigger actions based entirely on physical inventory. And how to precisely push and pull associated records using labels to maintain pipeline hygiene. Not to mention, acting as a digital bounty hunter, using dynamic inbound webhooks and the find action to hunt down records and eliminate expensive third-party software. It fundamentally changes the ceiling of what can be built in Go High Level. And as we wrap up, we want to leave you with a final thought to mull over. We used real estate and car dealerships as our primary examples today. But think about this. If you have the power to automate complex relationships between entirely custom data objects and external webhooks natively. What completely new business models, unique niches, or software-like services could your agency launch tomorrow that were technically impossible yesterday? Are you basically building lightweight SaaS products now without writing a single line of code? It is a fascinating question to bring to your next strategy meeting. Now, before we sign off, I need to remind you one last time. Do not forget to grab that free 30-day Go High Level trial. Having a full month to actually build out these transit hubs, set your webhooks loose, and test these cross-object actions is an opportunity you really shouldn't pass up. Exactly. That link with double the standard trial length is waiting for you in the show notes right now, so go click it. Have fun exploring the new architecture. Thanks for taking this deep dive with us today. Keep building, keep innovating, and we will catch you on the next one.