solid-orange•17h ago

Server URL Call-Ended

Configuring my serverURL using a custom webhook via make, but it triggered every second of the call. How do I change this so it only triggers my webhook for the Call-Ended event?

5 Replies

Vapi Support Bot•17h ago

Thanks for your question! To help you set your webhook to trigger only for the "Call-Ended" event, could you clarify how you are currently configuring your webhook in Make—are you able to set event filters (like "call-ended") in your scenario, or are you receiving all events and handling filtering in your webhook handler code? Source: - Vapi CLI Webhook Documentation

⤵️ Mention @Vapi Support Bot for follow-ups 🐥

Duckie•17h ago

Message marked as helpful by @raymoney! 🎉

solid-orangeOP•17h ago

I can set filters in make, but the amount of credits being consumed would not be sustainable. And I don’t have webhook handler code in make @Vapi Support Bot

Vapi Support Bot•17h ago

Currently, Vapi sends all event types (including "call-ended") to your server URL, and there is no built-in way to filter for only "call-ended" events at the Vapi configuration level.
If Make filtering is too costly, the recommended approach is to set up a lightweight webhook handler (for example, using a simple Node.js/Express server) that only forwards "call-ended" events to Make, reducing unnecessary triggers and credit usage.

// Example: Only forward "call-ended" events
app.post('/webhook', (req, res) => {
  if (req.body.type === 'call-ended') {
    // Forward to Make here
  }
  res.status(200).send();
});

// Example: Only forward "call-ended" events
app.post('/webhook', (req, res) => {
  if (req.body.type === 'call-ended') {
    // Forward to Make here
  }
  res.status(200).send();
});

For now, direct event filtering at the Vapi webhook configuration is not supported (see docs). Sources: - Server URLs - CLI Webhook Documentation

solid-orangeOP•17h ago

If anyone has a workaround for this it would be much appreciated

Server URL Call-Ended

Did you find this page helpful?