Let n8n Define the parameters - missing

I found this issue already logged (here Let AI define parameter Feature community), but replies closed.

The AI feature to let n8n define parameters has completely disappeared from my n8n. I’m self-hosting on community version 1.84.1. Several functions I want to complete rely on this and i can’t seem to resolve them without it.

e.g. passing parameters from a parent to child workflow, warning in node “No parameters are set up to be filled by AI. Click on the :sparkles: button next to a parameter to allow AI to set its value.”

Problem is, I don’t have this icon in ANY of my nodes any more.

{
“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”: ,
“schema”: ,
“attemptToConvertTypes”: false,
“convertFieldsToString”: false
}
},
“type”: “@n8n/n8n-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”: [

]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “cd44bef00794971c99adde49d78db1c45974570d35331f7c7a47d05012af71b4”
}
}

The latest update to the post above was from Niklas_Hatje (n8n Team) who said “yes, it should be on Community / all plans. Please let me know if that is not the case for you”.

Hoping he or someone from n8n team can help? Thank you :slight_smile: !

1 Like

have you updated your version recently? like did you notice it was gone after updating? or it just magically disappeared without updating?

Good question, i think it updated but not sure if it was recent - might be why its changed - any ideas how to fix without rolling back version?

same thing happend to me I upgraded to 1.88 and Let the model fill in the parameter disappeared

1 Like

Same here, is there a fix for this?

1 Like

can someone with this feature enabled export the workflow/node to check what’s set?

My last information was this:

{{ $fromAI("tool", "the selected tool to use") }}
{{ $fromAI('Tool_Parameters', ``, 'json') }}

I wish I could help you with that problem, yesterday I was studying about the MCPs and when it comes to assigning the parameters the option for the model to define the parameters it considers best is supposed to come up and it’s not my case either and it’s frustrating because now I’m stuck and I don’t know how to continue

I’m using version 1.89.2 in Railway and I am sure it is not because of Railway itself because the person I am learning from also did it from there (Although that yes, an earlier version) so my most likely guess is that it is a bug in this version… Hopefully 1.90.0 will fix this if this is the case.

same here, tried to update but nothing has changed

Same for me on Hostinger, it’s really annoying that n8n support isn’t responding.

This is a known issue with the MCP community node, it should be fixed in next weeks release more details on the issue itself 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 use our MCP node assuming you are using an SSE based MCP server and not stdio

1 Like

I still have this issue with version 1.99.1 - is it because I am self-hosting?!? It’s driving me mad

1 Like

Strange is, i see that feature in other nodes, mine wont work… same on version 1.99

1 Like

Hi @Kanati,

I think this is happening because you’re a sub-workflow which doesn’t define any inputs on the trigger. We now fetch these automatically, to define them go to “When Executed by Another Workflow” in your sub-workflow and make sure you have Define using fields below selected. in the Input Data Mode, then you should be able to define inputs for the subworkflow, and after refreshing your parent workflow you should be able to see them. Here’s a quick video:

Hope that helps!