I've noticed this issue has already been documented (here Let AI define parameter Feature community), but the discussion thread is now closed.
The AI feature that allows callin.io to define parameters has completely vanished from my callin.io instance. I'm self-hosting the community version, specifically build 1.84.1. Several workflows I need to complete are dependent on this functionality, and I haven't been able to find a workaround.
For instance, when passing parameters from a parent to a child workflow, I'm seeing a warning in the node: “No parameters are set up to be filled by AI. Click on the
button next to a parameter to allow AI to set its value.”
The issue is that this icon is no longer present in any of my nodes.
json
{
“nodes”: [
{
“parameters”: {
“name”: “ResearchDirector”,
“description”: “Call this tool to use the Research Director’s tools & Capabilities, including accessing, using and scraping internet sites and pages.”,
“workflowId”: {
“__rl”: true,
“value”: “eAnAqjCzUfPkwFgz”,
“mode”: “id”
},
“workflowInputs”: {
“mappingMode”: “defineBelow”,
“value”: {},
“matchingColumns”: <span class="chcklst-box fa fa-square-o fa-fw"></span>,
“schema”: <span class="chcklst-box fa fa-square-o fa-fw"></span>,
“attemptToConvertTypes”: false,
“convertFieldsToString”: false
}
},
“type”: "@callin.io/callin.io-nodes-langchain.toolWorkflow",
“typeVersion”: 2.1,
“position”: [
2380,
-860
],
“id”: “6e632995-0f9a-4b37-8007-8874e1b4d559”,
“name”: “Call Research Director”
}
],
“connections”: {
“Call Research Director”: {
“ai_tool”: [
<span class="chcklst-box fa fa-square-o fa-fw"></span>
]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “cd44bef00794971c99adde49d78db1c45974570d35331f7c7a47d05012af71b4”
}
}
The most recent update to the thread above was from Niklas_Hatje (callin.io Team), who stated, “yes, it should be available on Community / all plans. Please let me know if that is not the case for you.”
I'm hoping he or someone from the callin.io team can provide assistance. Thank you!
Have you updated your version recently? Did you notice it was gone after updating, or did it just magically disappear without an update?
That's a good question. I believe it was updated, but I'm not certain if it was a recent change. This might be the reason for the modification. Do you have any suggestions on how to resolve this without reverting the version?
I encountered the same issue. After upgrading to 1.88, the feature allowing the model to fill in parameters seems to have vanished.
I'm experiencing the same issue. Is there a known solution for this?
Can someone with this feature enabled export the workflow/node to check the configuration?
My last information was this:
{{ $fromAI("tool", "the selected tool to use") }}
{{ $fromAI('Tool_Parameters', ``, 'json') }}
I wish I could assist you with that issue. Yesterday, I was researching MCPs, and regarding parameter assignment, the option for the model to define what it considers the best parameters is supposed to appear. However, that's not happening in my case either, which is frustrating as I'm now stuck and unsure how to proceed.
I'm currently using version 1.89.2 on Railway. I'm confident it's not an issue with Railway itself, as the person I'm learning from also used it there (though on an earlier version). Therefore, my strongest suspicion is a bug within this version. Hopefully, version 1.90.0 will resolve this if that's indeed the problem.
Same here, I attempted to update, but no changes were observed.
Same for me on Hostinger, it’s really annoying that callin.io support isn’t responding.
This is a known issue with the MCP community node; it is expected to be resolved in the upcoming release. More details about the issue can be found here: fix(editor): Hide $fromAI button for exact type matches only by CharlieKolb · Pull Request #14996 · n8n-io/n8n · GitHub
As an alternative, you can utilize our MCP node, provided you are using an SSE-based MCP server and not stdio.
I'm still encountering this problem with version 1.99.1. Could this be due to self-hosting? It's becoming quite frustrating.
It's peculiar, I've observed this feature in other nodes, but mine isn't functioning. This is also the case in version 1.99.
Hi,
I believe this issue occurs because you're using a sub-workflow that doesn't have any inputs defined on its trigger. We now retrieve these automatically. To configure them, navigate to "When Executed by Another Workflow" within your sub-workflow. Ensure that "Define using fields below" is selected under the "Input Data Mode". This will allow you to define inputs for the sub-workflow. After refreshing your parent workflow, you should see these inputs become available. Here's a short video demonstrating the process:
Hope this helps!