Here's what's going on: I'm trying to have 2 server urls, one which connects to voiceglow and one which connects to make. Now the voiceglow url has to be in the server url section within the assistant configuration. This means that the server url for make has to be in the organization server url (Can't put it in tool because there's no function I think at least to trigger it whenever the call ends and then send all the information such as price, transcript, etc.) The problem here is priority. In the priority list the assistant server url ranks higher than the org server url. So I'm wondering how to hopefully give equal priority to both or maybe someone can tell me about a way to make a tool do the same exact thing as an assistant configuration url would do such as sending the transcript and triggering after the call has ended. Please let me know, Thanks.

@Mehul Rox It sounds like you're trying to integrate two different services with your VAPI assistant and are concerned about the priority in which server URLs are used to handle events. As per the current system design, events are only sent to one server URL based on the priority stack, with the assistant server URL taking precedence over the organization server URL. Unfortunately, there isn't a way to set equal priority for two server URLs within the VAPI system. However, you could consider a workaround by using the assistant server URL to handle the initial event and then programmatically forwarding the necessary data to the second server URL (for Make) after the initial processing is done by Voiceglow. This would involve setting up an endpoint on the Voiceglow server that, upon completion of its processing, makes an HTTP request to the Make server with the relevant data such as price, transcript, etc. Regarding the tool to trigger after the call has ended, if there is no existing function to handle this within the VAPI, you would need to implement this logic within your server-side application. The application would listen for a specific event indicating the call has ended, process the data as needed, and then forward it to the Make server. If you need more detailed guidance on how to set this up or if there are any specific functions within VAPI that could assist with this process, please ask support for more info on this. They may have additional insights or updates that could help you achieve your goal.

@Mehul Rox can you be more clear here?

Basically I want to have both the voiceglow url and the make.com webhook in the assistant configuration server url section but there is only option for 1 url. And tools dont work because they dont trigger after the call ends and send info such as transcripts and such.

@Mehul Rox voiceglow is for custom llm, then same make server url can be used for tools calling and end of call report using server event type differentiator.

llm?

hmm..

How can I use a single server url. For make it's creating a different webhook. and for voiceglow its automatically creating a url with "voiceglow runtime" something in it but its nothing like the one make.com makes

yeah i mean this.

but there is one problem

server event filter can be tried out.

Alright

you can remove use make stuff, if your finding it difficult then i suggest stick to what your doing.

Need some help here. Ive entered the url and made it to post. But what should I put as the body type and also are any headers or strings required? Im new to the http module https://cdn.discordapp.com/attachments/1293642220074700820/1294326429101723658/image.png?ex=670a9aec&is=6709496c&hm=70a51d8166e849614d0aab445279d731a3b4ae8f54eb24cb3fb4b50ab060c4c7&

@Mehul Rox can you join today's discord OH.