https://vapi.ai/ logo
Join Discord
Powered by
GHL NATIVE INTEGRATION
# support
g
Hi everyone where the direct integration with GHL ended up? I need to change my connected subaccount but the documentation isn’t up to date. https://docs.vapi.ai/tools/go-high-level I cannot integrate GHL anymore and I can’t disconnect the old subaccount apparently https://cdn.discordapp.com/attachments/1443687991821471947/1443687992211538020/1C3DCE90-0DB0-4970-9458-AFE26FE865C9.png?ex=698054f7&is=697f0377&hm=d7d995de43a46232f15b1c121d26e774afc1137fbe568f54547fe04ca0a0e0d2&
Where is this integration? In integrations there are only MCP and GHL to run workflows as tools
I hope you’re doing well. We’re running into an issue with our VAPI integration that I’d like to raise. Initially, we had connected VAPI to one GHL sub-account and everything worked fine. We tested it thoroughly, finalized the assistant with the appropriate prompts, and the industry-specific tool that we needed to excel in was working as expected. However, now we’re trying to connect VAPI to a different GHL sub-account. Previously, there was a direct integration option in VAPI where we could just authorize and connect easily. Now, Webbee is asking us to connect through the API. We added the new API key, but somehow, when a call is triggered in VAPI, the data is still being sent to the old sub-account instead of the new one. Could you please help us resolve this so that the integration works correctly with the new sub-account? Organization ID: 270df958-7b6f-4641-939e-aeb4b2c196d3 Thanks in advance for your assistance. Best regards,
@User
@User @User
c
Hi Giacomo, Thanks for the update. To help us investigate the routing issue, could you share a bit more information about your current GHL setup? Specifically: - The GHL sub-account you intend to connect - The old sub-account that Vapi is still sending data to - Any recent changes made in your GHL or Vapi integration settings Additionally, please provide a few recent call IDs where the assistant still routed data to the old sub-account. This will allow us to review the backend logs and pinpoint where the forwarding is occurring. Once we have these details, we can dig in and get this corrected for you. Thank you!
g
It’s absolutely ashaming the support, we have an email thread that now recived an automated reply asking for info are already in the thread. Nothing has been fixed in almost a month. The fact is that I’m not seeing anymore the ghl integration to set the api keys of the new subaccount
@User
New Subaccount ID: RO2RJFv3R3AZFphoNvLH Old Subaccount ID: pIsjTFoU7MxZQgwaUfJA Organization ID: 270df958-7b6f-4641-939e-aeb4b2c196d3
But anyways I don’t know how these information would help to fix just a front end miss in VAPI
Has nothing to do with GHL this issue
c
Hi Giacomo, Sorry for the delay in getting back to you, and thank you for your patience. Our team has reviewed this and confirmed that the native GHL integration is scheduled to be fixed in Q1 2026. We understand how important this feature is for your workflow, and we appreciate you bearing with us while the update is completed. If anything changes on the timeline or if early access becomes available, we’ll follow up immediately. Best regards, Vapi Support ---
g
It was working previously, why needed to be broken and fixed? There isn’t neither the “connect subaccount” anymore
It could take the chance to integrate more subaccount per VAPI account
And not only one
c
We have a fix that is pending review. Once it is tested, we will put the fix in the next release.
PreviousNext
Powered by