suraj_kumar1648
# general-english
s
@Vapi I am using the prompt as follows:- [Identity] You are Lisa, an AI voice assistant to help users generate a quotation to provide an estimation of installing solar panels on their rooftops. [Task] 1. Ask the user their name: "To get started, can I have your name?" 2. Once you have their name, ask their address: "Can you please let me know the address where you want to get the solar installed? Please include house number, street name, city, and state." 3. Trigger the getGeocodedAddress tool using the provided address. 4. If the response is successful, parse the details like city, country, googlePlaceId, latitude, longitude, postalCode, state and streetName from the response. 5. Now trigger the tool 'getAddress' using the above details like city, country, googlePlaceId, latitude, longitude, postalCode, state and streetName. 6. From the response of
getAddress
, parse the data.address_id . 7. Now ask user for their monthly electricity bill in dollars. 8. Use the
createProposal
tool with the following inputs: - `addressId`: Use the address_id from the previous tool response. - `annualConsumptionInWh`: 0. - `avgMonthlyBillInDollars`: user will tell this. - `customerName`: Retrieve from conversation. - `organizationId`: "674eb324343c73b7ec34ce79". 9. Say: "Thank you for providing the information. I am evaluating weather data, your home rooftop, and solar radiance to generate a solar quotation. Please wait for a few seconds." 10. End the call. But in this, the tool createProposal is not able to parse addressId from the response of getAddress Please help
v
@Suraj_Kumar It seems like there might be an issue with how the
addressId
is being handled between the
getAddress
tool and the
createProposal
tool. To ensure that the
addressId
is correctly parsed and passed to the
createProposal
tool, you might want to double-check the following: 1. Ensure that the
getAddress
tool is being called with the correct parameters and that it is returning a successful response with the necessary data. 2. Verify that the
addressId
is being correctly extracted from the
getAddress
tool's response. 3. Confirm that the
addressId
is being passed in the correct format to the
createProposal
tool. If you've checked these steps and the issue persists, there might be a technical glitch or a requirement for additional troubleshooting. In such cases, it's best to reach out to the support team with specific details of the issue for further assistance. Please ask support for more info on this.
s
The response from getAddress tool is { "status": "success", "message": "address saved successfully", "data": { "address_id": "67611a8e96c96c57ef98be59" } } @Vapi
v
@Suraj_Kumar Great! It looks like the
getAddress
tool is working correctly and has provided you with an
address_id
. You can now use this
address_id
as a parameter for the
createProposal
tool. Make sure to pass the
address_id
value exactly as it is, including any hyphens or special characters, to ensure proper functionality. If you need assistance with the next steps or have any other questions, feel free to ask!
s
while doing it, the tool createProposal is using addressId as "123456" which is a random value. @Vapi
v
@Suraj_Kumar It seems there might be a mistake in the way the
address_id
is being passed to the
createProposal
tool. You should ensure that the
address_id
you received from the
getAddress
tool response is correctly used when calling
createProposal
. Instead of the placeholder "123456", you should use "67611a8e96c96c57ef98be59" as the
addressId
. If you're ready to proceed with the correct
address_id
, I can help you with that. Would you like to go ahead and use the correct
address_id
for the
createProposal
tool now?
s
Yes
@Vapi
v
@Suraj_Kumar Great! To proceed with using the correct
address_id
for the
createProposal
tool, you'll need to replace the placeholder "123456" with the actual
address_id
you received, which is "67611a8e96c96c57ef98be59". If you're ready, go ahead and call the
createProposal
tool with the correct
address_id
. If you need any assistance with the call or have any other questions, feel free to ask!
s
What changes should I do in prompt @Vapi
v
@Suraj_Kumar To ensure the
createProposal
tool receives the correct
address_id
, you should modify the prompt that calls this tool by replacing the placeholder
addressId
value with the actual
address_id
you received from the
getAddress
tool. Here's how you can adjust the prompt: 1. Identify the part of your prompt or code where
createProposal
is being called. 2. Locate the parameter where
addressId
is set to "123456". 3. Replace "123456" with the actual
address_id
value "67611a8e96c96c57ef98be59". For example, if your current prompt or code looks something like this:
Copy code
json
{
  "tool": "createProposal",
  "parameters": {
    "addressId": "123456",
    // ... other parameters ...
  }
}
You should change it to:
Copy code
json
{
  "tool": "createProposal",
  "parameters": {
    "addressId": "67611a8e96c96c57ef98be59",
    // ... other parameters ...
  }
}
Make sure to include any other necessary parameters that the
createProposal
tool requires. Once you've made this change, you can execute the prompt, and the
createProposal
tool should use the correct
address_id
. If you need further assistance with this process or have any other questions, please let me know!
s
@Vapi I am using VAPI dashborad for this
v
@Suraj_Kumar If you're using the VAPI dashboard to interact with the tools, you'll need to manually update the
addressId
field when setting up the
createProposal
action. Here's what you should do: 1. Navigate to the section of the VAPI dashboard where you can initiate the
createProposal
tool. 2. Look for the input field where
addressId
is entered. 3. Replace the placeholder value "123456" with the actual
address_id
you received, which is "67611a8e96c96c57ef98be59". 4. Ensure all other required fields are filled in correctly. 5. Submit the action to execute the
createProposal
tool with the correct
address_id
. If you encounter any issues or if the dashboard does not seem to be updating the
addressId
correctly, it might be a good idea to reach out to the VAPI support team for assistance. They can guide you through the process or help resolve any technical difficulties you might be facing. Should you need further clarification or help, please let me know!
s
@User Please help here
s
Hey @Suraj_Kumar 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!
3 Views