How can I send a post call webhook
hey folks, does anyone have a beginner guide how to send a post call webhook to a make automation? Thank you! I have the sdk but i have no idea what to update.
VTo send a post-call webhook to your Make automation, set your assistant's
Vapi will POST an
Source:
server.url to your Make webhook endpoint. For example, in your assistant configuration:Vapi will POST an
end-of-call-report event to this URL after each call, which Make can use to trigger your automation. For more details on the payload, see the Vapi server events documentation.Source:
⤵️ Mention @Vapi Support Bot for follow-ups 🐥
A@Duckie where do i make that edit, how do i see and edit my bots code
Awhere do i make that edit, how do i see and edit my bots code
VTo edit your bot's server URL for post-call webhooks, go to the Vapi dashboard, select your assistant, and in the Advanced tab, set the Server URL field to your Make webhook endpoint:
Save your changes, and Vapi will send post-call events to this URL automatically.
For more details, see the Vapi server URL documentation.
Source:
Save your changes, and Vapi will send post-call events to this URL automatically.
For more details, see the Vapi server URL documentation.
Source:
Ahow do i do it from the dashboard? if i add a server url that is a make webhook will it impact anything else?
A@Duckie how do i do it from the dashboard? if i add a server url that is a make webhook will it impact anything else? Secondly, in the webhook data is there the call trancript?
VYes, the webhook data sent to your Make endpoint includes the call transcript.
You'll find it in the
You can use this field in your Make automation to access the full call transcript.
See more in the Vapi server events documentation.
Source:
You'll find it in the
transcriptend-of-call-report payload. For example:You can use this field in your Make automation to access the full call transcript.
See more in the Vapi server events documentation.
Source:
A@Duckie is it possible to only run that webhook on the end of call reports rather than 5 times a call?
VYou can't configure Vapi to only send webhooks for
In your Make scenario, add a filter after the webhook module:
This ensures only
See Vapi server events documentation for event types.
Source:
end-of-call-report events, but you can filter them in your Make automation. In your Make scenario, add a filter after the webhook module:
This ensures only
end-of-call-report events trigger further actions in your automation, while other event types are ignored. See Vapi server events documentation for event types.
Source:
A@Vapi Support Bot any idea how I can control costs? make charges me everytime the scenario runs, but 1/5 scenarios will be the right one
VHi, to get better understanding of the cost please refer to our pricing page https://vapi.ai/pricing
AThanks Aditya, I meant from the perspective of, during the call the make webhook runs like 10 times because it is firing for every "status update", so it cost a make credit every single time. i would love to avoid firing the make webhook every time, only on the "end of call report"
VHi, do this set assistant.serverMessages to endOfCall report only.
YGuys, both N8N and Make charge by workflow executions,
this renders VAPI unusable because you cannot send specific post-call webhooks.
I had to create a zapier account specially for that purpose using premium subscription (pro)
in order to be able to filter all the numerous events that are not the "end-of-call-report"
since Zapier filters (when enabled) do not count as an execution which is a big plus,
and actually the only offering i found to have this feature, unless you want to host
your own API endpoint and provision it...
A Vapi conversation can create hundreds of events, imagine each execution would cost you money...
The problem with Zapier is that they do not support wbhook responses, thus
you cannot execute a webhook and get back a custom response as an api call would expect,
this is besides that issue but just to keep in mind, while N8N and make do support this essential.
So i eventually stopped using VAPI and started using Eleven Labs agents (Conversational AI)
since you get a nice post-call webhook that is always fired, and it comes with an HMAC key
to verify the payload as well. (also because of the low audio quality compared to an 11Labs agent
my clients complained about that)
Guys at Vapi, please listen to users and try to think as a user,
it's not enough to have a running agent, the post-processing
is more important or at least as important as the runtime itself,
and you should make it easier for developers, add another specific
endpoint or filter to send only end-of-call, this would bring many developers
to you, because many of us use automations and your current paradigm is an anti-pattern.
Also I've been complaining about the fact that agent does not speak first with many
of the TTS providers, which again renders it useless using these, again besides
the point... I'm ranting here because i had high hopes for Vapi, but those "small" things...
this renders VAPI unusable because you cannot send specific post-call webhooks.
I had to create a zapier account specially for that purpose using premium subscription (pro)
in order to be able to filter all the numerous events that are not the "end-of-call-report"
since Zapier filters (when enabled) do not count as an execution which is a big plus,
and actually the only offering i found to have this feature, unless you want to host
your own API endpoint and provision it...
A Vapi conversation can create hundreds of events, imagine each execution would cost you money...
The problem with Zapier is that they do not support wbhook responses, thus
you cannot execute a webhook and get back a custom response as an api call would expect,
this is besides that issue but just to keep in mind, while N8N and make do support this essential.
So i eventually stopped using VAPI and started using Eleven Labs agents (Conversational AI)
since you get a nice post-call webhook that is always fired, and it comes with an HMAC key
to verify the payload as well. (also because of the low audio quality compared to an 11Labs agent
my clients complained about that)
Guys at Vapi, please listen to users and try to think as a user,
it's not enough to have a running agent, the post-processing
is more important or at least as important as the runtime itself,
and you should make it easier for developers, add another specific
endpoint or filter to send only end-of-call, this would bring many developers
to you, because many of us use automations and your current paradigm is an anti-pattern.
Also I've been complaining about the fact that agent does not speak first with many
of the TTS providers, which again renders it useless using these, again besides
the point... I'm ranting here because i had high hopes for Vapi, but those "small" things...
YPlease see my reply, you can use Zapier which filters out those events you don't need so you don't pay for them.
I hope Vapi does bring this feature, as i think post call should be treated differently then "during" call events.
I hope Vapi does bring this feature, as i think post call should be treated differently then "during" call events.
VI sincerely apologize for the delayed response to your support request.
We implemented better tracking for support tickets to ensure timely responses going forward, but due to a technical limitation, this only applies to tickets created after this past week.
I'm closing this older ticket, but if your issue still needs attention, please:
Reply with 'REOPEN' or
Email support@vapi.ai with any updates
I'll personally ensure your new request gets prompt attention.
Thank you for your patience.
Best regards,
Vapi Support Team
We implemented better tracking for support tickets to ensure timely responses going forward, but due to a technical limitation, this only applies to tickets created after this past week.
I'm closing this older ticket, but if your issue still needs attention, please:
Reply with 'REOPEN' or
Email support@vapi.ai with any updates
I'll personally ensure your new request gets prompt attention.
Thank you for your patience.
Best regards,
Vapi Support Team
