Set up tools when modifying assistant from API
# support
s
Hello I am doing outbound calls, and I modfy the system prompt for each call with data on my customer. I have tools attached to my Assistant, but for some reason they do not work (seems like the assistant doesnt have access to them)
@Vapi
v
@Skan Hello! I'm here to help you with your Voice API needs. If you're having trouble with the tools attached to your Assistant, let's try to troubleshoot the issue together. Could you please provide me with more details about the tools you're trying to use and the specific problems you're encountering? This will help me assist you more effectively.
s
Custom tools I built on my server
@Vapi
v
@Skan I understand that you have custom tools built on your server that you're trying to use with your Assistant. To assist you better, I would need to know the following: 1. How are these tools integrated with your Assistant? Are they supposed to be called via an API or some other method? 2. What error messages or behavior are you observing that indicates the tools are not working as expected? 3. Have there been any recent changes to your system or the custom tools that might have affected their functionality? Once I have more context, I can provide you with more targeted assistance. If the issue is beyond my capabilities, I may suggest reaching out to support for more in-depth help.
s
The problem is that when I call a phone number with the assistant attached to it the tools work. when i trigger an outbound call through the API after updating the system prompt and the initial message (through the API as well), the tools seem to never get triggered as if the assistant didnt have access to them
@Vapi
v
@Skan It sounds like the issue may be related to the way the outbound calls are being initiated through the API, which might be affecting the assistant's access to the custom tools. Here are a few steps you can take to troubleshoot the problem: 1. **Check API Permissions**: Ensure that the API key or credentials you're using for outbound calls have the necessary permissions to access and trigger the custom tools. 2. **Review API Call Configuration**: Verify that the API call to initiate the outbound call is correctly configured, including the system prompt and initial message, and that it's properly set up to trigger the custom tools. 3. **Inspect Logs**: Look at the server logs where the custom tools are hosted to see if there are any incoming requests from the outbound calls. This can help determine if the issue is with the request not being sent or not being received. 4. **Test Tools Independently**: Try triggering the custom tools independently of the outbound call process to ensure they are working as expected. 5. **API Documentation**: Double-check the API documentation to make sure you're using the correct endpoints and parameters for triggering the custom tools during outbound calls. 6. **Contact Support**: If you've gone through these steps and the issue persists, it may be best to contact the support team for the API or the platform you're using for further assistance. If you need help with any of these steps or have additional information that could help diagnose the issue, please let me know!
s
Not solved
@User can you help here?
v
@Skan Hello! I'm here to help you with your outbound calls and ensure your system prompts are customized correctly for each customer. It sounds like there might be an issue with the tools attached to your Assistant. Let's try to troubleshoot this together. Could you please provide me with more details about the tools you're trying to use and the specific problems you're encountering? This will help me understand the situation better and assist you more effectively.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
s
Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help me figure out what went wrong!