Variable names not appearing in subsequent modules

Hi there and welcome to the callin.io Community!

Have you tried running the webhook at least once to capture the data structure? If not, this might be the cause of the issue. The variable you've indicated seems to have been added manually, but it doesn't actually exist within the module being invoked.

Best regards,

P.S. You can paste your screenshots directly into the forum. There's no need to upload and share them via Google Drive.

Thanks for the suggestion! Yes, I've already tried that approach, and it's actually how I typically configure a scenario. Unfortunately, I'm still encountering the same issue.

If you could share an export of your scenario, someone might be able to test it on their end and help diagnose the issue. Providing sample data would also be beneficial, particularly if it involves a POST webhook rather than a GET URL.

Hi,

I've loaded the exported blueprint. Here's an example cURL call (executed from a Mac terminal):

bash
curl -X PUT ‘< https://hook.eu2.callin.io/gnv4db85b23o3aptif49h9qao6qgrdry>’


This returns:

json
{ "results": [ { "toolCallId": ", "result": "The time is: 15:12" } ] }


The variable I need to populate is the toolCallId, which isn't available from the selection, as shown in the screenshot.

Thanks,
Simon
simpleScenario.json (5.8 KB)

I've figured out my mistake. I initially used callin.io for the test call, which provided the missing callerID. Since that call had issues, I attempted to isolate the scenario using a cURL call. As that cURL call doesn't provide the toolCallId, the tool doesn't offer it as a variable within the scenario.

Hi,

Okay, I believe I understand the issue. It seems you're invoking the URL without any parameters.

Here’s what you should do:

1. Select your webhook and redefine the data structure.

image766×413 50.5 KB

2. Invoke it like this, and the webhook will understand the expected incoming data:

https://hook.eu2.make.com/gnv4db85b23o3aptif49h9qao6qgrdry?toolCallId=12345&result=The+time+is%3A+15%3A12

3. You will then be able to utilize the result in the final webhook of your scenario.

image1534×525 84.4 KB

L

That’s great, thanks.

Great! If this resolves your issue, please consider marking it as the solution. This helps others who encounter the same problem find the answer more easily.

Just to close this off - I ran the following from the command line (mac terminal):

bash
curl -X PUT ‘< https://hook.eu2.callin.io/gnv4db85b23o3aptif49h9qao6qgrdry?toolCallId=12345>’


As that passes in toolCallId, this then reappears in the second webhook when I want to define the outgoing datastructure. The reason for the confusion was that I had originally called this from callin.io (which supplies toolCallId) and subsequently wanted to test it using curl calls.