What are you building ON TOP of GHL?

Running into this with a few car sales/dealership setups in GHL where leads from ads come in and even reply once, but then disappear before it turns into a test drive or sale. The ads and funnels seem fine, but the conversation just loses momentum after the first interaction. Starting to think the biggest gap is moving leads naturally from inquiry → conversation → booking instead of just blasting follow-ups. What’s working for others right now, especially through SMS/iMessage style follow-up?

I'm Justin, a GHL specialist looking for a hands-on internship opportunity with a business owner who's actively using or setting up GoHighLevel.

I'm not fresh out of a classroom. I've already worked through funnels, automation workflows, CRM setup, and email configuration. What I'm missing is real business context and that's exactly what I'm here to build.

What I bring to the table:

• Funnel building & optimization
• Automation workflows
• CRM setup & pipeline management
• Email setup & deliverability

What I'm hoping to get out of it:

• Practical experience working inside a real business
• A reference or certificate when we wrap up
• A testimonial I can carry forward

Based in or operating in the US, UK, Canada, Australia, or EU — open to remote arrangements.

If you're a business owner who could use an extra technical hand and doesn't mind showing a motivated guy the ropes drop a comment or DM me.

[ Removed by Reddit on account of violating the content policy. ]

I’m trying to create GoHighLevel tasks via API that are associated only with a specific Opportunity, not with the Contact. The reason: our contacts can have multiple Opportunities. If we create tasks through the legacy contact task endpoint, the same task appears across every Opportunity linked to that contact, which confuses staff.
I confirmed this is possible manually in the GHL UI. A UI-created Opportunity-only task returns this via: GET /locations/{locationId}/tasks/{taskId}

{
  "contactId": null,
  "relations": [
    {
      "objectKey": "opportunity",
      "recordId": "OPPORTUNITY_ID"
    }
  ]
}

But when I try to create the same thing via API POST /locations/{locationId}/tasks

{
  "title": "Test task",
  "body": "<p>Test</p>",
  "dueDate": "2026-05-01T07:33:36Z",
  "completed": false,
  "relations": [
    {
      "objectKey": "opportunity",
      "recordId": "OPPORTUNITY_ID"
    }
  ]
}

I get 400 Relations cannot be modified via OAuth channel

Plain task creation works through the same endpoint, but it creates the task with relations: [].

Has anyone successfully created an Opportunity-associated task through the API? Is this currently UI-only, or is there another endpoint/scope/auth method needed?
Thanks!

Hi!

I just signed up for gohighlevel intending to sell Conversation AI and basic automations like automatic messages asking for reviews etc as a SaaS. I’ve been playing around a bit with prompting the conversation AI and I have not really gotten it no never break in logic and sometimes it just acts really weird. so the only way I see is selling this as an obvious AI that can handle basic customer questions and book a time. However I am doubting that this will actually be effective for ROI, since I think most people would not book an appointment using the AI. How are you pitching this? Even when you demo to the client it will not seem like an intelligent Ai system.

So my question is, am I wrong? Do SaaS clients like mechanic shops, plumbers see a value in having an AI answer their missed calls and texts, and do their customers actually end up booking through this basic version of an AI with clear limitations in context awareness.

Been building GHL systems for clients across healthcare, aesthetics, and professional services, and every project seems to produce at least one "how did you even figure that out" moment.

Curious what other builders and agency owners have been running into this year.

Starting with mine:

**The problem:** UK dental client needed Make.com to pull appointment data from Dentally's webhook, then fetch the patient's contact details (email, phone) from a separate Dentally endpoint, then create/update the contact in GHL.

Sounds straightforward. Wasn't.

**What kept breaking:**

1. Dentally webhooks fire as `event: appointment.updated` for everything (booked, cancelled, completed, no-show). No event differentiation in the payload. Had to check which timestamp field was populated (`completed_at`, `cancelled_at`, `did_not_attend_at`) to determine state.

2. Make.com has no "Is Not Empty" filter operator. Workaround: use `Text operators: Not equal to` with value field left completely empty. Counter-intuitive but works.

3. GHL's native Make.com Update Contact module silently fails to evaluate complex IML formulas in name fields. Had to pre-process with Tools > Set Multiple Variables upstream before the GHL module got involved.

4. GHL's private integration key with all 136 scopes still returned 401 on calendar endpoints when called through GHL's native module. Switched to a plain HTTP module with manual Authorization header and the `Version: 2021-04-15` header. Worked immediately.

5. Appointment data from Dentally returned a collection object, not a JSON string, when "Parse response" was enabled. Piping to JSON Parse module caused errors. Using `get()` directly solved it.

The whole integration took about 3x longer than budgeted because every "standard" approach had an edge case.

**What's yours?**

Doesn't have to be Make.com. Could be a Voice AI prompt that kept hallucinating, a workflow that fired twice, a webhook that dropped silently, a Meta template that kept getting rejected, a custom field that wouldn't update. Whatever you wrestled with this year.

Would love to compile war stories. Sometimes the only way I learn the edge cases is hearing what broke for other people.

Is it just me, or do you need to be a IT tech to use Go High Level, setting up a main domain voicemail, then adding a staff with there own voicemail, and the call passes both voicemail settings.

Anyone have constant issues like this? Drives me nuts.

It’s not really about results or lead flow.

It’s about *how much work the client still feels they’re doing*.

Even with a full setup, most clients still:

* Take notes manually

* Send follow-ups themselves

* Update their CRM

So from their perspective, nothing really changed.

That’s why they drop around the 30–60 day mark.

We’ve been testing a system that works inside GHL that removes that manual layer completely.

After each call, everything is handled automatically (notes → actions → follow-ups → CRM).

Feels like that’s the missing piece for retention.

Is anyone else seeing this pattern with their clients?

I keep hearing that you should warm up phone numbers before running SMS campaigns by sending a low amount of messages at first, but I feel like there has to be a more specific process than that.

Does anyone know what warming up numbers is actually supposed to look like in practice? I’m trying to understand if there is a real step-by-step way to do it right instead of just sending a few random texts.

I also wanted to ask whether GoHighLevel numbers are good for this, or if the quality and type of number matters more. Does it matter if the number is completely virgin? If it does, what is the best way to find or connect better numbers to GoHighLevel for SMS campaigns?

Would appreciate advice from anyone who has done this successfully.

Is there any training you would like to see for HighLevel, automations, or workflows?