I'm working on integrating VAPI.ai with Make.com for handling inbound calls. I need to send the Call ID to Make.com when the call connects, as this Call ID is required for use in later modules within the workflow. However, I'm encountering difficulties in sending the Call ID at the time of connection. Can you suggest a solution to correctly pass the Call ID to Make.com during the call connection process?

@Fouzantanveer Certainly! To send the Call ID to Make.com when a call connects, you'll need to set up a webhook in VAPI that triggers on call connection events. This webhook should be configured to send data to a Make.com webhook URL that you've set up to receive the call event data. Here's a general outline of the steps you need to follow: 1. Configure a Webhook in VAPI: - Go to your VAPI dashboard and set up a new webhook. - Choose the event type that corresponds to call connections (e.g.,

onCallConnected

). - Enter the Make.com webhook URL where the data should be sent. 2. Include Call ID in Webhook Payload: - Ensure that the payload sent to Make.com includes the Call ID. This is typically included by default, but you should verify that it's part of the data being sent. 3. Set Up Make.com to Receive the Call ID: - In your Make.com scenario, set up a webhook module to receive incoming webhooks. - Use the data from the incoming webhook, which includes the Call ID, in subsequent modules within your workflow. 4. Test the Integration: - Make a test call to ensure that the webhook is triggered and the Call ID is sent to Make.com. - Check the logs in both VAPI and Make.com to verify that the data is being transmitted correctly. If you're still having trouble, please ensure that: - The webhook URL from Make.com is correctly entered in VAPI. - The event type selected in VAPI is the correct one for call connections. - The metadata you're sending includes the Call ID. If you've checked all of these and the issue persists, you might need to look into the specific configurations of your VAPI and Make.com setup. If you need further assistance with the specific configurations or troubleshooting, please ask support for more info on this.

How to setup webhook in VAPI

@Fouzantanveer To set up a webhook in VAPI for handling inbound calls and sending the Call ID to Make.com, you would typically follow these steps: 1. Access the VAPI Dashboard: - Log in to your VAPI account and navigate to the dashboard where you can manage webhooks. 2. Create a New Webhook: - Look for a section labeled 'Webhooks', 'Events', 'Integrations', or something similar. - Click on the option to create a new webhook. 3. Configure Webhook Settings: - Enter the URL provided by Make.com where the webhook should send data. This URL is your Make.com webhook receiver endpoint. - Select the event that should trigger the webhook. In your case, you want the webhook to fire when a call connects, so choose the 'Call Connected' event or equivalent. - If there are options to customize the payload, make sure the Call ID is included. 4. Save and Activate the Webhook: - Save your webhook configuration. - Ensure that the webhook is set to active so that it will trigger when the specified event occurs. 5. Test the Webhook: - Perform a test call to ensure that the webhook is working as expected. - Check the logs in Make.com to confirm that it is receiving the Call ID. Please note that the exact steps and terminology may vary depending on the version and interface of VAPI you are using. If you need more detailed instructions or if there is a specific area where you are encountering difficulties, please let me know, and I can provide further assistance. If the information provided here does not match the interface or options you see in your VAPI dashboard, it's best to consult the official VAPI documentation or reach out to their support team for guidance.

Hey @Fouzantanveer you can use end of call report it contains the call id, did you tried it?

@Shubham Bajaj yes that's right, but I want call ID as soon as the call connects as my other modules of scenario would be using call ID to locate that call/row in Google sheets.

Hey @Fouzantanveer check this docs in this only the first two points are relevant for your use, when Vapi makes a request it sends call object as well in the payload which contains the call id. As it's done right before the call is connected you will have everything right at start of the call. https://shmbajaj.notion.site/Setting-Up-Dynamic-Variables-for-Your-Vapi-Calls-A-Quick-Guide-14077ff426238037b101f91a446f7f6a?pvs=4