function result from make not being received
# support
r
I'm getting an error with a custom tool I set up I am sending over the correct data via my make.com scenario where it watches for call, uses gpt and responds to call. But my assistant is saying she was unable to find the right state for the zip code although I am sending the correct info over.. Here's what my script looks like within my prompt: “Great, I was just able to check and my system confirms the benefit is still available in {lookupState result}" And here's my instructions included in the prompt: Instructions for using the lookupState function: When the client provides their Zip Code, use the lookupState function in order to match the correct State to the Zip Code so you can confirm it back to the client before moving forward. Use the result from the function as the State to verify. The function will give you the State you should confirm as the result. Do not confirm the State until you have received the response from the function. The State will be responded to you via the function under the parameter "Result" https://cdn.discordapp.com/attachments/1266251906465140740/1266251906918125638/image.png?ex=66a4787c&is=66a326fc&hm=889fe119306c428c0551b9d066f92d4de23418639162188c7624729bc086d329&
Here's what I'm finding in my call log: { "name": "lookupState", "role": "tool_call_result", "time": 1721967408602, "result": "No result returned.", "toolCallId": "call_sBT9oMBWpCXVLWnKgm2n6a6R", "secondsFromStart": 74.182 }
v
message has been deleted
@rob It seems like there might be an issue with the integration between your custom tool and the assistant's response. To troubleshoot this, I would recommend checking the following: 1. Ensure that the
lookupState
function is being called correctly within your scenario. Verify that the Zip Code is being passed as a parameter to the function and that the function is set up to return the correct state. 2. Confirm that the
lookupState
function is working as expected by testing it independently with known Zip Codes and checking if the correct states are returned. 3. Check the data flow between the
lookupState
function and the assistant's script. Make sure that the result from the
lookupState
function is being correctly captured and inserted into the script where
{lookupState result}
is mentioned. 4. If the
lookupState
function is asynchronous, ensure that the assistant's script waits for the function to complete and retrieve the result before attempting to use it in the response. If you've verified all these points and the issue persists, it might be helpful to look at the logs or any error messages you're receiving for more detailed troubleshooting. If you need further assistance with this, please provide more specific details or error messages you're encountering.
You can continue this conversation by mentioning me in the message.
Got it. Tagging @User for additional help.
s
@rob please share the call id.
r
Resolved- was using wrong response