https://vapi.ai/ logo
Join Discord
Powered by
Unable to web call Squad
# support
n
Hi, I have created a Squad via API and was trying to Web Call it via Vapi's website. But I just get this error (attached image). Note I do not use assistantOverrides option at all, this must be UI adding it. Squad ID - 9d9377ac-9866-41c9-adb5-90a46cd5e163 https://cdn.discordapp.com/attachments/1459914354848829481/1459914355779833856/image.png?ex=697a1ab2&is=6978c932&hm=eb35df7bcca26cd305fab50ad7e45f2d3916fc727800d32cfda7f7bf54c4fb71&
c
Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team
Hi, Could you provide the Squad configuration JSON to me? it will help me better understand where the "name should not exists" error comes from. You can find squad configuration from Vapi Dashboard -> Squads -> -> "" Button left of "Call" button. Please copy and send the entire JSON here. If possible, please provide the request you sent when you first created the squad using the API.
n
Squad config from Vapi Dashboard
Api config when creating squad via API
c
Hi, I reviewed the configuration. I wasnt able to find anything wrong with it. Could you try deleting this squad and try creating a new one? Could you also confirm the following? • Did the API request to create the squad succeeded? • If yes, Did that new squad show up in the dashboard without any errors? • Did the error start occurring when you try to edit something in the squad from the UI? If so, could you please tell me what changes you made which triggered this error?
n
I have tried creating again and I am still getting the same issue (new squad id - 
47a7a73f-7ff7-412a-9684-8c5b02019181
). Re your questions: Yes API succeeded. Squad showed up without any errors. Error start occuring straight await, after I create it using API.
c
I was not able to find anything wrong with the new squad id, so I suspect this might be a frontend issue. If you dont mind, could you add me in your organization? I can take a look into the squad and help figure out the issue. My email is: bharath@vapi.ai
n
Sure, I have added you to my org. Thanks
c
Hey, thanks for adding me. I reviewed the squad and it looks like you have added the transferCall tool to the test - interaction assistant as an inbuilt tool, this caused a json structure check to fail, thus returning 400 error. If you want to transfer to another assistant in the squad, you can use the hand off tool which you can see in the squad UI., or go to your assistant page and add a transfer call tool there, and then go to the squad. For now I have removed the transfer call tool which was causing the issue.
n
So what is the difference between hand off and transfer call tools?
So I was using trasnferCall tool due to the following configurations -
Copy code
"assistantDestinations" => [
   %{
    "assistantName" => "Eval call_assistant - Interaction",
    "message" => "",
    "transferMode" => "swap-system-message-in-history-and-remove-transfer-tool-messages",
    "type" => "assistant"
  }
]
and changing to the following configurations have actually worked (thank you for the advice) -
Copy code
"assistantDestinations" => [
  %{
    "assistantName" => "xyz - Interaction",
    "contextEngineeringPlan" => %{"type" => "all"},
    "type" => "assistant"
  }
],
So I have few questions. 1. Are the previously mentioned two configurations result in the same behaviour? Is there any difference, if yes how can I make the hand off behave exactly the same as my previous transferCall? 2. Does contextEngineeringPlan "all" include system message from previous assistant and hand off tool call? I would like to have the same behaviour as "swap-system-message-in-history-and-remove-transfer-tool-messages".
c
Hi @N3squik, The difference between transferCall and hand off tool boils down to where they are used. Hand off tools is designed to be used for multi agent systems (i.e, for squads). And this hand off tool is configured in your squads section. Think of hand off tool as an "addon" to your existing assistant. Whereas, the transferCall tool is baked into your assistant settings, this can also be used to transfer between assistants, but this has to be configured in the assistant settings, not in the squads settings. What you did in your configuration was, you configured the transferCall tool as a Handoff tool. As an "addon" to your assistant, which caused confusion in the structure validation on Vapi and started throwing errors.
n
okay thank you, could you please confirm that what I posted above is equivalent and if you could answer some of the queries I raised, that would be great!
c
The two configurations are similar, but the first one is a transferCall, which should be configured from the assistant's page. The second configuration is for handoff, which you can configure it in the squads settings itself. Yes, the contextEgineeringPlan "all" will include all messages from the previous assistant and pass it down to the next assistant during handoff.
n
Is it possible to use "swap-system-message-in-history-and-remove-transfer-tool-messages" on the handoff tool?
c
Hi, Only the provided examples in the docs are possible to use in the handoff tool more information here: https://docs.vapi.ai/squads/handoff
PreviousNext
Powered by