https://vapi.ai/ logo
Join Discord
Powered by
dynamic transfer call webhook not wokring
# support
y
Call ID: bd36bcc4-af42-4728-9e9e-b8b93f43176b
t
Same or similar issue here. VAPI stopped sending transfer-destination-request seemingly out of nowhere at around 3:30pm EST Friday.
s
I am having the same issue as well! Seems like a bug. Can someone please help!
c
The main issue is that you have "destinations": \[\] in your transfer tool configuration. For dynamic transfers with transfer-destination-request, you need to either: 1. Remove the destinations property entirely (recommended) 2. Don't provide an empty array - this tells Vapi that destinations are pre-defined Once you remove the destinations property, the AI will call your dynamicTransfer function, and Vapi will send a transfer-destination-request webhook to your server URL for you to validate and provide the final destination. Try updating your transfer tool configuration by removing the "destinations": \[\] line and you should start receiving the webhook events!
y
@Vapi Maybe you guys should fix the document pls
call id: d42da8fe-a727-4b26-bfc7-8c05946f8ba9
I also observe a intersting thing is the forwarding number is using the "content" as the number
c
You can try these two configurations to see if they work for you: option 1:
Copy code
{
  "parameters": {
    "type": "object",
    "properties": {
      "destination": {
        "type": "string",
        "description": "The number to transfer the call to. In the format of E.164 default country code is +1"
      }
    },
    "required": [
      "destination"
    ]
  }
}
option 2:
Copy code
{
  "parameters": {
    "type": "object",
    "properties": {
      "destination": {
        "type": "string",
        "description": "The number to transfer the call to. In the format of E.164 default country code is +1"
      }
    },
    "required": [
      "destination"
    ]
  }
}
y
but I also want LLM to generate the content, how can I set the content that I want LLM to say?
This is my webhook logic
Copy code
console.error(
                    "[ZONIC-VAPI-WEBHOOK] No transfer number provided in function call parameters",
                );
                throw new Error("Transfer number is required");
            }

            console.log(`[ZONIC-VAPI-WEBHOOK] Transferring to: ${number} with message: "${content}"`);

            // Return the transfer destination response
            const response: VapiTransferDestinationResponse = {
                destination: {
                    type: "number",
                    number: number,
                    message: {
                        type: "request-start",
                        content: content,
                    },
                },
            };
that is exactly same from option 1 and option 2
Tested still not working...
It still not sending the transfer-destination-request to my webhook
but nothing has sent to webhook, even in webhook logs doesn't show it
c
Could you please share the call id for the call made from the screenshot you sent?
n
Any update on this? I followed the same tutorial and am not seeing any webhooks coming through. With or without the destinations array
I found a 
handoff-destination-request
with the handoff tool in the API, but it just hangs and never does a hdnoff, though I am not sure what the response should be from the webhook because it is not documented anywhere
c
Hey Noah, the handoff tool is for assistant-to-assistant transfers, so if you are trying to transfer to an external destination we recommend sticking with the regular transferCall tool. Here are some guidelines for ensuring the transfer-destination-request webhook gets sent: 1. Enable the server event in your assistant configuration 2. Configure a dynamic transfer tool without pre-defined destinations 3. Set up a proper webhook endpoint that returns the destination 4. Ensure your webhook URL is accessible and responds quickly If you're still not receiving webhooks after following these steps, check your assistant configuration in the Vapi dashboard to verify that both the serverEvents and serverUrl are properly set.
n
That makes sense. We did get assistant-to-assistant transfers working
c
Glad you were able to get this resolved. If anything else comes up or you need further assistance, we’re here to help.
b
Facing the exact same issue here even after removing the 
destination
entirely, I can't get VAPI to fire the 
transfer-destination-request
event - I've opened a ticket with my test Call IDs here https://discord.com/channels/1211482211119796234/1417235104404734075
c
Thanks for flagging it. We will respond to that ticket instead and close this one out.
3 Views
PreviousNext
Powered by