https://vapi.ai/ logo
Join Discord
Powered by
Call Recordings are Not Logged in Go High Level
# support
s
Hi Vapi Support Team, Has there been a change in how call recordings are pulled from Vapi and logged into Go High Level? I have not made any changes to my workflows or call recording URLs. I was able to see all the logged calls in Go High Level yesterday. When I checked today, I could not see any of the logged calls on Go High Level anymore. This change affected all the existing calls as well as new calls from today. I did see that I'm supposed to use call.artifact.recording to get the URL, but I tried many different variations of that and it did not work. I'm not sure if this is more of a Vapi or Go High Level issue. The attached picture shows how I got the recording URL before and it worked up until today. I even tried changing the format of the recording to mp3 and it still didn't work. Thanks! https://cdn.discordapp.com/attachments/1375124884220547123/1375124884635521074/image.png?ex=68308c59&is=682f3ad9&hm=4ab3709d531e3259cf5664d2c619b672e931375a81cc4d8fd4cc04e344eff866&
v
It appears Vapi recently deprecated the old recording URL properties and now requires using 
Call.artifact.recording
for call recordings ([see changelog](https://docs.vapi.ai/changelog/2025/4/29)). To help pinpoint the issue: Have you updated your Go High Level integration or workflow to reference the new 
Call.artifact.recording
property, and if so, are you seeing any errors or missing data in the integration logs? This will help determine if the issue is with the new data format or with how Go High Level is processing it. Source: - [Vapi Changelog April 29, 2025](https://docs.vapi.ai/changelog/2025/4/29)
To troubleshoot the missing call recording URLs, please verify that your webhook handler is still receiving the 
recordingUrl
in the payload. The correct property should look like this in the webhook JSON:
Copy code
json
{
  "artifact": {
    "recordingUrl": "https://..."
  }
}
Double-check that your template uses 
{{inboundWebhookRequest.message.artifact.recordingUrl}}
and that the webhook payload from Vapi still includes this field. If the field is missing, it may indicate a change or issue on the Vapi side; otherwise, the problem may be with how Go High Level processes the webhook. Source: - [Vapi API Reference: List Calls](https://docs.vapi.ai/api-reference/calls/list)
s
I still see it in the webhook payload. I also tried using call.artifact.recording and used the stereo recording and combined mono recording. I couldn't get it to work
k
Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!
s
This is happening to all of my calls. I can no longer listen to any of my previous calls or any new ones from today on Go High Level. This is just one example: 006bcbcb-06db-4b1d-8d27-1267a09c0571.
k
Hey Selina, I have replied to your email over this GSL issue, so now I want you to know, do you want to continue here or over the email?
For your reference, we are sending the end-of-call report to your provided GHL server URL, and it's returning a 200 HTTP response code. This means that there is something wrong with your GHL side, so you have to look there.
s
I will continue here. I checked with GHL and they said they could not replicate the issue. They thought it was a vapi issue.
v
Suggestion: Since the Vapi webhook payload still includes 
artifact.recordingUrl
, try testing your integration with a simple payload like below to confirm GHL is parsing it correctly:
Copy code
json
{
  "artifact": {
    "recordingUrl": "https://your-recording-url.com/recording.wav"
  }
}
If this test payload works in GHL, the issue may be with how GHL handles the new structured 
artifact.recording
object. Double-check any custom mapping or parsing logic in GHL for changes needed after the Vapi schema update. Sources: - [Vapi Changelog April 29, 2025](https://docs.vapi.ai/changelog/2025/4/29) - [Vapi API Reference: List Calls](https://docs.vapi.ai/api-reference/calls/list)
Actionable Suggestion: Update your Go High Level integration to use the new property path for call recordings:
Copy code
liquid
{{inboundWebhookRequest.message.artifact.recording.monoUrl}}
or, for stereo:
Copy code
liquid
{{inboundWebhookRequest.message.artifact.recording.stereoUrl}}
Make sure you are not using 
artifact.recordingUrl
or 
call.artifact.recording
directly, as these are deprecated or incorrect. This should resolve the issue if the webhook payload includes the new structure. Sources: - [Vapi Changelog April 29, 2025](https://docs.vapi.ai/changelog/2025/4/29) - [Vapi API Reference: List Calls](https://docs.vapi.ai/api-reference/calls/list)
k
Hey Selina, it's not related to VAPI. You confirm from the shared CSV file with you over the email. Let me know if I can help with anything else.
PreviousNext
Powered by