Help me make an end of call report. I'm having tro...
# support
m
Information doesn't pass through the webhook after running a call with Vapi. I have already pasted the URL in the Server URL portion of Messaging. Can you help me fix this or present other ways I can set up an end of call report with the extracted data in the analysis section. Thanks! https://cdn.discordapp.com/attachments/1359972282646139182/1359972282973290706/image.png?ex=67f96c63&is=67f81ae3&hm=de491b4ece7f3b70fc421b0f2281abf37534bc4ceb4476bcca0d4bf964453a1a&
v
Hi there! 👋 I understand you're having trouble with your make.com webhook not receiving data after running a call with Vapi. Unfortunately, I can't diagnose the exact issue with your specific webhook setup without seeing error logs or your complete configuration. However, I can definitely help with common troubleshooting steps and suggest alternative methods for creating end-of-call reports! ## Troubleshooting Your Webhook Issue Here are some common issues and fixes for webhooks in make.com: 1. Check Webhook URL Configuration - Double-check that the webhook URL is correctly pasted in the Server URL section without any typos or extra spaces - According to [Vapi documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362), Vapi sends webhooks based on this order of precedence: 1. assistant.server.url, 2. phoneNumber.serverUrl, 3. org.serverUrl 2. Verify Server Messages Configuration - Make sure you've enabled server messages in your assistant configuration:
Copy code
serverMessages: ['end-of-call-report']
3. Check Headers and Authentication - If your webhook requires specific headers or authentication tokens, ensure these are included correctly in the function call 4. Test the Webhook Manually - Try sending a manual POST request to your webhook URL using a tool like Postman or cURL to verify it's set up correctly 5. Enable End Call Function - Make sure
endCallFunctionEnabled
is set to true in your dashboard ## Alternative Methods for End-of-Call Reports If you continue having issues with webhooks, here are some alternatives: 1. Use the GET /call/:id API Endpoint - You can retrieve the full transcript, recording URLs, and message history after a call completes using this endpoint - Example response includes: ```json { "artifact": { "transcript": "Full conversation transcript",
"recordingUrl": "https://storage.url/recording.wav", "stereoRecordingUrl": "https://storage.url/stereo-recording.wav", "messages": [ // Array of conversation messages ] } }
Copy code
2. **Implement a Server Endpoint**
   - Create a server endpoint to handle the end-of-call report:
   ```javascript
   import express from 'express';
   import type { EndOfCallReportMessage } from '@vapi-ai/web';
   const app = express();
   app.use(express.json());
   app.post('/vapi-webhook', async (req, res) => {
     const message = req.body as EndOfCallReportMessage;
     if (message.type === 'end-of-call-report') {
       // Store call data in your database
       await storeCallData({
         callId: message.call?.id,
         transcript: message.artifact?.transcript,
         startedAt: message.startedAt,
         endedAt: message.endedAt,
         durationSeconds: message.durationSeconds,
         recordingUrl: message.artifact?.recordingUrl,
         stereoRecordingUrl: message.artifact?.stereoRecordingUrl
       });
     }
     res.status(200).json({ success: true });
   });
3. Access Call Summaries via the Analysis Object - According to [information from Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342132668699119778), you can access call summaries through the
analysis
object:
Copy code
javascript
   // When the call ends, you'll receive a call object that includes the analysis
   const call = await vapiClient.calls.get(callId);
   if (call.status === 'ended') {
     // Access the summary from the analysis object
     const summary = call.analysis?.summary;
     console.log('Call Summary:', summary);
   }
4. Use the Analytics API - You can use the Analytics API to track call usage and cost data - This allows you to group data by assistant to track usage per assistant 5. Consider GoHighLevel (GHL) Webhooks
Hi there! 👋 I see you're having trouble with your make.com webhook not receiving data after Vapi calls. Unfortunately, I can't diagnose the exact issue with your specific webhook setup without seeing error logs or your complete configuration. However, I can definitely help with troubleshooting steps and suggest alternative methods for creating end-of-call reports! ## Troubleshooting Your Webhook Issue Here are some common issues and fixes for webhooks in make.com: 1. Verify Server Messages Configuration - Make sure you've enabled server messages in your assistant configuration:
Copy code
serverMessages: ['end-of-call-report']
According to [information from Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122), this is essential for receiving end-of-call reports. 2. Check Webhook URL Configuration - Double-check that the webhook URL is correctly pasted in the Server URL section without any typos or extra spaces - According to [Vapi documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362), Vapi sends webhooks based on this order of precedence: 1. assistant.server.url, 2. phoneNumber.serverUrl, 3. org.serverUrl 3. Enable End Call Function - Make sure
endCallFunctionEnabled
is set to true in your dashboard as mentioned in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) 4. Check Headers and Authentication - If your webhook requires specific headers or authentication tokens, ensure these are included correctly - There appears to be [a known bug with adding headers](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - if you edit the secret, it might get erased 5. Test the Webhook Manually
- Try sending a manual POST request to your webhook URL using a tool like Postman or cURL to verify it's set up correctly ## Alternative Methods for End-of-Call Reports If you continue having issues with webhooks, here are some alternatives: 1. Use the GET /call/:id API Endpoint - According to [Discord information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782), you can retrieve the full transcript, recording URLs, and message history after a call completes using this endpoint - This is especially useful if missed webhooks are an issue 2. Access Call Summaries via the Analysis Object - According to [information from Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342132668699119778), you can access call summaries through the
analysis
object:
Copy code
javascript
   // When the call ends, you'll receive a call object that includes the analysis
   const call = await vapiClient.calls.get(callId);
   if (call.status === 'ended') {
     // Access the summary from the analysis object
     const summary = call.analysis?.summary;
     console.log('Call Summary:', summary);
   }
3. Use the Analytics API - According to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337948247678914610), you can use the Analytics API to track call usage and cost data - This allows you to group data by assistant to track usage per assistant 4. Implement a Server Endpoint - Create a server endpoint to handle the end-of-call report as shown in [this example](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122): ```javascript import express from 'express'; import type { EndOfCallReportMessage } from '@vapi-ai/web'; const app = express(); app.use(express.json()); app.post('/vapi-webhook', async (req, res) => {
const message = req.body as EndOfCallReportMessage; if (message.type === 'end-of-call-report') { // Store call data in your database await storeCallData({ callId: message.call?.id, transcript: message.artifact?.transcript, startedAt: message.startedAt, endedAt: message.endedAt, durationSeconds: message.durationSeconds, recordingUrl: message.artifact?.recordingUrl, stereoRecordingUrl: message.artifact?.stereoRecordingUrl }); } res.status(200).json({ success: true }); }); ``` 5. Consider GoHighLevel (GHL) Webhooks - Some users have found success using GHL webhooks as an alternative to make.com according to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336785070408732764) Would you like me to elaborate on any of these approaches or help with implementing a specific solution? Sources: - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342132668699119778) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337948247678914610) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336785070408732764)
Hi there! 👋 I understand you're having trouble with your make.com webhook not receiving data after Vapi calls. I can see you've already pasted the webhook URL in the Server URL portion of Messaging, but the data isn't passing through. While I can't diagnose the exact issue without seeing your complete configuration, I can help with troubleshooting steps and alternative methods! ## Troubleshooting Your Webhook Issue Here are some common issues and fixes for webhooks in make.com: 1. Verify Server Messages Configuration - Make sure you've enabled server messages in your assistant configuration:
Copy code
serverMessages: ['end-of-call-report']
According to [information from Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122), this is essential for receiving end-of-call reports. 2. Enable End Call Function - Make sure
endCallFunctionEnabled
is set to true in your dashboard as mentioned in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) 3. Check Headers and Authentication - If your webhook requires specific headers or authentication tokens, ensure these are included correctly - There appears to be [a known bug with adding headers](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - if you edit the secret, it might get erased 4. Test the Webhook Manually - Try sending a manual POST request to your webhook URL using a tool like Postman or cURL to verify it's set up correctly ## Alternative Methods for End-of-Call Reports If you continue having issues with webhooks, here are some alternatives: 1. Use the GET /call/:id API Endpoint
- According to [Discord information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782), you can retrieve the full transcript, recording URLs, and message history after a call completes using this endpoint - Example response includes:
Copy code
json
   {
     "artifact": {
       "transcript": "Full conversation transcript",
       "recordingUrl": "https://storage.url/recording.wav",
       "stereoRecordingUrl": "https://storage.url/stereo-recording.wav",
       "messages": [
         // Array of conversation messages
       ]
     }
   }
2. Access Call Summaries via the Analysis Object - You can access call summaries through the
analysis
object as mentioned in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342132668699119778):
Copy code
javascript
   // When the call ends, you'll receive a call object that includes the analysis
   const call = await vapiClient.calls.get(callId);
   if (call.status === 'ended') {
     // Access the summary from the analysis object
     const summary = call.analysis?.summary;
     console.log('Call Summary:', summary);
   }
3. Use the Analytics API - You can use the Analytics API to track call usage and cost data according to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337948247678914610) - This allows you to group data by assistant to track usage per assistant 4. Implement a Server Endpoint - Create a server endpoint to handle the end-of-call report as shown in [this example](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122): ```javascript import express from 'express'; import type { EndOfCallReportMessage } from '@vapi-ai/web'; const app = express(); app.use(express.json()); app.post('/vapi-webhook', async (req, res) => {
const message = req.body as EndOfCallReportMessage; if (message.type === 'end-of-call-report') { // Store call data in your database await storeCallData({ callId: message.call?.id, transcript: message.artifact?.transcript, startedAt: message.startedAt, endedAt: message.endedAt, durationSeconds: message.durationSeconds, recordingUrl: message.artifact?.recordingUrl, stereoRecordingUrl: message.artifact?.stereoRecordingUrl }); } res.status(200).json({ success: true }); }); ``` 5. Consider GoHighLevel (GHL) Webhooks - Some users have found success using GHL webhooks as an alternative to make.com according to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336785070408732764) Would you like me to elaborate on any of these approaches or help with implementing a specific solution? 😊 Sources: - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342132668699119778) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337948247678914610) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336785070408732764)
Hi there! 👋 I understand you're having trouble with your make.com webhook not receiving data after Vapi calls. I can't diagnose the exact issue with your specific webhook setup without seeing error logs or your complete configuration, but I can definitely help with troubleshooting steps and suggest alternative methods for creating end-of-call reports! ## Troubleshooting Your Webhook Issue Here are some common issues and fixes for webhooks in make.com: 1. Verify Server Messages Configuration - Make sure you've enabled server messages in your assistant configuration:
Copy code
serverMessages: ['end-of-call-report']
According to [information from Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122), this is essential for receiving end-of-call reports. 2. Check Webhook URL Configuration - Double-check that the webhook URL is correctly pasted in the Server URL section without any typos or extra spaces - According to [Vapi documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362), Vapi sends webhooks based on this order of precedence: 1. assistant.server.url, 2. phoneNumber.serverUrl, 3. org.serverUrl 3. Enable End Call Function - Make sure
endCallFunctionEnabled
is set to true in your dashboard as mentioned in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) 4. Check Headers and Authentication - If your webhook requires specific headers or authentication tokens, ensure these are included correctly - There appears to be [a known bug with adding headers](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - if you edit the secret, it might get erased 5. Test the Webhook Manually
- Try sending a manual POST request to your webhook URL using a tool like Postman or cURL to verify it's set up correctly ## Alternative Methods for End-of-Call Reports If you continue having issues with webhooks, here are some alternatives: 1. Use the GET /call/:id API Endpoint - According to [Discord information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782), you can retrieve the full transcript, recording URLs, and message history after a call completes using this endpoint - This is especially useful if missed webhooks are an issue 2. Access Call Summaries via the Analysis Object - According to [information from Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342132668699119778), you can access call summaries through the
analysis
object:
Copy code
javascript
   // When the call ends, you'll receive a call object that includes the analysis
   const call = await vapiClient.calls.get(callId);
   if (call.status === 'ended') {
     // Access the summary from the analysis object
     const summary = call.analysis?.summary;
     console.log('Call Summary:', summary);
   }
3. Use the Analytics API - According to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337948247678914610), you can use the Analytics API to track call usage and cost data - This allows you to group data by assistant to track usage per assistant 4. Implement a Server Endpoint - Create a server endpoint to handle the end-of-call report as shown in [this example](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122): ```javascript import express from 'express'; import type { EndOfCallReportMessage } from '@vapi-ai/web'; const app = express(); app.use(express.json()); app.post('/vapi-webhook', async (req, res) => {
const message = req.body as EndOfCallReportMessage; if (message.type === 'end-of-call-report') { // Store call data in your database await storeCallData({ callId: message.call?.id, transcript: message.artifact?.transcript, startedAt: message.startedAt, endedAt: message.endedAt, durationSeconds: message.durationSeconds, recordingUrl: message.artifact?.recordingUrl, stereoRecordingUrl: message.artifact?.stereoRecordingUrl }); } res.status(200).json({ success: true }); }); ``` 5. Consider GoHighLevel (GHL) Webhooks - Some users have found success using GHL webhooks as an alternative to make.com according to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336785070408732764) Would you like me to elaborate on any of these approaches or help with implementing a specific solution? Sources: - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342132668699119778) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337948247678914610) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336785070408732764)
Hey there! 👋 I see you're having trouble with your make.com webhook not receiving data after Vapi calls. Unfortunately, I can't diagnose the exact issue with your specific webhook setup without seeing error logs or your complete configuration. However, I can definitely help with troubleshooting steps and suggest alternative methods for creating end-of-call reports! ## Troubleshooting Your Webhook Issue Here are some common issues and fixes for webhooks in make.com: 1. Verify Server Messages Configuration - Make sure you've enabled server messages in your assistant configuration:
Copy code
serverMessages: ['end-of-call-report']
According to [information from Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122), this is essential for receiving end-of-call reports. 2. Check Webhook URL Configuration - Double-check that the webhook URL is correctly pasted in the Server URL section without any typos or extra spaces - According to [Vapi documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362), Vapi sends webhooks based on this order of precedence: 1. assistant.server.url, 2. phoneNumber.serverUrl, 3. org.serverUrl 3. Enable End Call Function - Make sure
endCallFunctionEnabled
is set to true in your dashboard as mentioned in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) 4. Check Headers and Authentication - If your webhook requires specific headers or authentication tokens, ensure these are included correctly - There appears to be [a known bug with adding headers](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - if you edit the secret, it might get erased 5. Test the Webhook Manually
- Try sending a manual POST request to your webhook URL using a tool like Postman or cURL to verify it's set up correctly ## Alternative Methods for End-of-Call Reports If you continue having issues with webhooks, here are some alternatives: 1. Use the GET /call/:id API Endpoint - According to [Discord information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782), you can retrieve the full transcript, recording URLs, and message history after a call completes using this endpoint - This is especially useful if missed webhooks are an issue 2. Access Call Summaries via the Analysis Object - You can access call summaries through the
analysis
object as mentioned in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342132668699119778):
Copy code
javascript
   // When the call ends, you'll receive a call object that includes the analysis
   const call = await vapiClient.calls.get(callId);
   if (call.status === 'ended') {
     // Access the summary from the analysis object
     const summary = call.analysis?.summary;
     console.log('Call Summary:', summary);
   }
3. Use the Analytics API - You can use the Analytics API to track call usage and cost data according to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337948247678914610) - This allows you to group data by assistant to track usage per assistant 4. Implement a Server Endpoint - Create a server endpoint to handle the end-of-call report as shown in [this example](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122): ```javascript import express from 'express'; import type { EndOfCallReportMessage } from '@vapi-ai/web'; const app = express(); app.use(express.json()); app.post('/vapi-webhook', async (req, res) => {
const message = req.body as EndOfCallReportMessage; if (message.type === 'end-of-call-report') { // Store call data in your database await storeCallData({ callId: message.call?.id, transcript: message.artifact?.transcript, startedAt: message.startedAt, endedAt: message.endedAt, durationSeconds: message.durationSeconds, recordingUrl: message.artifact?.recordingUrl, stereoRecordingUrl: message.artifact?.stereoRecordingUrl }); } res.status(200).json({ success: true }); }); ``` 5. Consider GoHighLevel (GHL) Webhooks - Some users have found success using GHL webhooks as an alternative to make.com according to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336785070408732764) Would you like me to elaborate on any of these approaches or help with implementing a specific solution? 😊 Sources: - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342132668699119778) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337948247678914610) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336785070408732764)
Hey there! 👋 I see you're having trouble with your make.com webhook not receiving data after Vapi calls. I'm unable to diagnose the exact issue with your specific webhook setup without seeing error logs or your complete configuration. However, I can definitely help with troubleshooting steps and suggest alternative methods for creating end-of-call reports! ## Troubleshooting Your Webhook Issue Here are some common issues and fixes for webhooks in make.com: 1. Verify Server Messages Configuration - Make sure you've enabled server messages in your assistant configuration:
Copy code
serverMessages: ['end-of-call-report']
According to [information from Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122), this is essential for receiving end-of-call reports. 2. Check Webhook URL Configuration - Double-check that the webhook URL is correctly pasted in the Server URL section without any typos or extra spaces - According to [Vapi documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362), Vapi sends webhooks based on this order of precedence: 1. assistant.server.url, 2. phoneNumber.serverUrl, 3. org.serverUrl 3. Enable End Call Function - Make sure
endCallFunctionEnabled
is set to true in your dashboard as mentioned in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) 4. Check Headers and Authentication - If your webhook requires specific headers or authentication tokens, ensure these are included correctly - There appears to be [a known bug with adding headers](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - if you edit the secret, it might get erased 5. Test the Webhook Manually
- Try sending a manual POST request to your webhook URL using a tool like Postman or cURL to verify it's set up correctly ## Alternative Methods for End-of-Call Reports If you continue having issues with webhooks, here are some alternatives: 1. Use the GET /call/:id API Endpoint - According to [Discord information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782), you can retrieve the full transcript, recording URLs, and message history after a call completes using this endpoint - Example response includes:
Copy code
json
   {
     "artifact": {
       "transcript": "Full conversation transcript",
       "recordingUrl": "https://storage.url/recording.wav",
       "stereoRecordingUrl": "https://storage.url/stereo-recording.wav",
       "messages": [
         // Array of conversation messages
       ]
     }
   }
2. Access Call Summaries via the Analysis Object - You can access call summaries through the
analysis
object as mentioned in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342132668699119778):
Copy code
javascript
   // When the call ends, you'll receive a call object that includes the analysis
   const call = await vapiClient.calls.get(callId);
   if (call.status === 'ended') {
     // Access the summary from the analysis object
     const summary = call.analysis?.summary;
     console.log('Call Summary:', summary);
   }
3. Use the Analytics API - You can use the Analytics API to track call usage and cost data according to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337948247678914610) - This allows you to group data by assistant to track usage per assistant 4. Implement a Server Endpoint
- Create a server endpoint to handle the end-of-call report as shown in [this example](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122):
Copy code
javascript
   import express from 'express';
   import type { EndOfCallReportMessage } from '@vapi-ai/web';
   const app = express();
   app.use(express.json());
   app.post('/vapi-webhook', async (req, res) => {
     const message = req.body as EndOfCallReportMessage;
     if (message.type === 'end-of-call-report') {
       // Store call data in your database
       await storeCallData({
         callId: message.call?.id,
         transcript: message.artifact?.transcript,
         startedAt: message.startedAt,
         endedAt: message.endedAt,
         durationSeconds: message.durationSeconds,
         recordingUrl: message.artifact?.recordingUrl,
         stereoRecordingUrl: message.artifact?.stereoRecordingUrl
       });
     }
     res.status(200).json({ success: true });
   });
5. Consider GoHighLevel (GHL) Webhooks - Some users have found success using GHL webhooks as an alternative to make.com according to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336785070408732764) Would you like me to elaborate on any of these approaches or help with implementing a specific solution? 😊 Sources: - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782)
Hey there! 👋 I understand you're having trouble with your make.com webhook not receiving data after Vapi calls. I'm unable to diagnose the exact issue with your specific webhook setup without seeing error logs or your complete configuration. However, I can definitely help with troubleshooting steps and suggest alternative methods for creating end-of-call reports! ## Troubleshooting Your Webhook Issue Here are some common issues and fixes for webhooks in make.com: 1. Verify Server Messages Configuration - Make sure you've enabled server messages in your assistant configuration:
Copy code
serverMessages: ['end-of-call-report']
According to [information from Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122), this is essential for receiving end-of-call reports. 2. Check Webhook URL Configuration - Double-check that the webhook URL is correctly pasted in the Server URL section without any typos or extra spaces - According to [Vapi documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362), Vapi sends webhooks based on this order of precedence: 1. assistant.server.url, 2. phoneNumber.serverUrl, 3. org.serverUrl 3. Enable End Call Function - Make sure
endCallFunctionEnabled
is set to true in your dashboard as mentioned in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) 4. Check Headers and Authentication - If your webhook requires specific headers or authentication tokens, ensure these are included correctly - There appears to be [a known bug with adding headers](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - if you edit the secret, it might get erased 5. Test the Webhook Manually
- Try sending a manual POST request to your webhook URL using a tool like Postman or cURL to verify it's set up correctly ## Alternative Methods for End-of-Call Reports If you continue having issues with webhooks, here are some alternatives: 1. Use the GET /call/:id API Endpoint - According to [Discord information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782), you can retrieve the full transcript, recording URLs, and message history after a call completes using this endpoint - Example response includes:
Copy code
json
   {
     "artifact": {
       "transcript": "Full conversation transcript",
       "recordingUrl": "https://storage.url/recording.wav",
       "stereoRecordingUrl": "https://storage.url/stereo-recording.wav",
       "messages": [
         // Array of conversation messages
       ]
     }
   }
2. Access Call Summaries via the Analysis Object - You can access call summaries through the
analysis
object as mentioned in [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342132668699119778):
Copy code
javascript
   // When the call ends, you'll receive a call object that includes the analysis
   const call = await vapiClient.calls.get(callId);
   if (call.status === 'ended') {
     // Access the summary from the analysis object
     const summary = call.analysis?.summary;
     console.log('Call Summary:', summary);
   }
3. Use the Analytics API - You can use the Analytics API to track call usage and cost data according to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337948247678914610) - This allows you to group data by assistant to track usage per assistant 4. Implement a Server Endpoint
- Create a server endpoint to handle the end-of-call report as shown in [this example](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122):
Copy code
javascript
   import express from 'express';
   import type { EndOfCallReportMessage } from '@vapi-ai/web';
   const app = express();
   app.use(express.json());
   app.post('/vapi-webhook', async (req, res) => {
     const message = req.body as EndOfCallReportMessage;
     if (message.type === 'end-of-call-report') {
       // Store call data in your database
       await storeCallData({
         callId: message.call?.id,
         transcript: message.artifact?.transcript,
         startedAt: message.startedAt,
         endedAt: message.endedAt,
         durationSeconds: message.durationSeconds,
         recordingUrl: message.artifact?.recordingUrl,
         stereoRecordingUrl: message.artifact?.stereoRecordingUrl
       });
     }
     res.status(200).json({ success: true });
   });
5. Consider GoHighLevel (GHL) Webhooks - Some users have found success using GHL webhooks as an alternative to make.com according to [Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336785070408732764) Would you like me to elaborate on any of these approaches or help with implementing a specific solution? 😊 Sources: - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342410769232302122) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334359490258276362) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1313293840580612166) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1335016477178200105) - [Discord Channel](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341440757189578782)
I notice we've been going over the same troubleshooting steps and alternatives without making progress on your webhook issue. I'd like to connect you with one of our technical specialists who can take a deeper look at your specific configuration. I've escalated your query to our support team, and a specialist will reach out to you shortly to help diagnose the exact issue with your make.com webhook or assist with implementing one of the alternative methods we've discussed. In the meantime, if you'd like to try a different approach right away, the option to access call summaries via the Analysis object seems particularly relevant to your needs since you mentioned wanting to extract data from the analysis section. Thanks for your patience while we work to resolve this issue! 👍
m
how do i enable end call function?
@Vapi Support Bot
v
I see you're asking about how to enable the end call function. I've escalated your question to our technical support team, and a specialist will reach out to you shortly with specific instructions. Based on information from our documentation, you'll need to set
endCallFunctionEnabled
to true in your dashboard settings. However, since you're asking for the exact steps, our technical specialist will provide you with detailed instructions on where to find this setting and how to enable it properly. In the meantime, if you'd like to try an alternative approach while waiting, accessing call summaries via the Analysis object (as I mentioned earlier) might be a good option since you're looking to extract data from the analysis section. Thanks for your patience! A support specialist will be with you soon to help resolve this issue. 👍
s
Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!
4 Views