Hi @Shubham Bajaj , I need some help. I’m building an outbound calling agent that will be triggered from GoHighLevel (GHL). The process involves sending lead details like name, number, and other info from GHL to Make.com, which will then trigger an outbound call using VAPI. After the call ends, I want to update the lead information back in GHL. For this, I need the contact ID to be sent back to another Make.com scenario, which will handle the update in GHL. I’m looking for a way to send the contact ID from Make.com to VAPI and then have it included in the end-call reports from VAPI back to Make.com. Can you advise if this is possible, and if so, how it can be implemented?

@Ch Adeel Absolutely, I can guide you through this process. To achieve the workflow you're describing, you'll need to ensure that the contact ID from GHL is passed through Make.com to VAPI when the outbound call is initiated. Here's a high-level overview of how you can implement this: 1. **From GHL to Make.com**: When a lead is triggered in GHL, send the lead details, including the contact ID, to Make.com using a webhook or GHL's built-in integration features. 2. **Make.com to VAPI**: In your Make.com scenario, configure an HTTP request module to trigger an outbound call with VAPI. Include the contact ID in the payload you send to VAPI. This can typically be done by adding a custom parameter in the API request that you're sending to VAPI. 3. **VAPI Configuration**: Ensure that your VAPI setup is configured to accept custom parameters and include them in the call details. You might need to modify your VAPI call setup to capture and log the contact ID. 4. **End-Call Report**: Once the call ends, VAPI should send the call report back to Make.com. Ensure that the call report includes the contact ID. This might involve configuring the call report structure in VAPI to include the custom parameters received at the start of the call. 5. **Make.com to GHL**: Finally, use another Make.com scenario to catch the end-call report from VAPI, extract the contact ID, and update the lead information in GHL accordingly. If you need specific instructions on how to configure the HTTP request in Make.com or how to set up the call report structure in VAPI, please let me know, and I can provide more detailed steps. If there are any functions or configurations within VAPI that you're not sure about, please ask support for more info on this.

@Shubham Bajaj can you please look at this?

@Ch Adeel Yes it is possible, you have to use dynamic variables using assistant overrides. Checkout this documentation on setting dynamic variables https://vapi.notion.site/Setting-Up-Dynamic-Variables-for-Your-Vapi-Calls-A-Quick-Guide-140008c8393f8057ac24db4089edc466?pvs=4

Hello @Shubham Bajaj .I can pass variables to our assistant, but I need to send them back to Make.com as part of the end-call report. While I can send variables through a tool call, I also need the call transcript included. Is there a way to include these variables in the end-call report?

Yes they are included in end of call report by default under the call object as assistant overrides.

@Shubham Bajaj Thanks for your help; I’m now able to get the contact ID. However, there’s another issue. When I initiate a call through the HTTP module in Make.com, it shows the request is successful, but no call is actually made. The logs indicate the customer ended the call, and the transcript shows it hit voicemail. However, the customer says they didn’t receive any call. Interestingly, when I initiate an outbound call directly from the VAPI dashboard to the same number, everything works perfectly. Could you help me understand what might be causing this?

@Shubham Bajaj hey buddy please reply to my queries in DM

@Ch Adeel create a new support ticket, add this description over there with failing call ids.