AI Agents | Tools Configuration | Current vs Past Versions [Past is better]

Feedback
1

Hi,
I have seen that the latest versions of n8n (e.g., 1.99.1) do not have the same configuration in the following:

Previously, when you wanted to add a tool to an AI Agent, you were able to name the parameter in which the response to the execution is submitted (Field to Return) and also input predefined variables (Extra Workflow Inputs).

I can’t find those options when creating new tools using the current version of n8n.

Why is this feedback important? To be able to connect our AI Agents with static information from a user, like their Record ID in our CRM, we need to be able to obtain static information that is coming from the AI Agent Workflow.

Additionally, to be able to optimize the use of tools, it is great to have a defined parameter that contains the submit output tool (Field to Return), because sometimes I use the tools also as workflows for other automations, and I include other field outputs in the last node executed. If I use the current tool node it causes problem for it includes irrelevant information in the last node.

This is the perfect tool configuration we require for being able to create more professional workflows. Please include this in the coming versions or include both but please never take them out for most of my professional workflows require from it.

Schema of Tool n8n
Schema of Tool n8n490×788 34.9 KB

2

create the subworkflow for that tool, in the trigger(WHEN EXECUTES BY THE OTHER), set the variables you defined in the aia agent system prompt, and after try add new tool, choose the new subworkflow and will be dinamically populated.

the issue here is that i cannot define the tool name/function name itself in the tool node.

3

Hi

Yes, the part of defining the variables can be managed with the sub-workflow. Problem is that, when optimizing the creation of workflows, we may have more than one “response” field.

In the previous versions we had “Field to return” with that we could “filter” from all of those fields a specific parameter name that we wanted to be considered in the response generation.

With the new version it will take all the information in the last node → Which can affect when you also use the workflow for other cases (That are not only agent tools)

For the name of the tool I think the node name is being used

4

I hope so :grinning_face:…

BTW, I still have in some workflows the old tool node for ai agent(the case where you can define all values)… it will be a problem if I keep using it? I think at a point a version will be deprecated, and may break :thinking:…