[BUG] Custom Tool Override Configuration Broken in Flowise v2.2.3

[heslanx]

Describe the bug
In Flowise version 2.2.3, the ability to override custom tool configurations using overrideConfig.customToolName, overrideConfig.customToolDesc and overrideConfig.customToolShema is not functioning as expected.

To Reproduce
Steps to reproduce the behavior:

1. Open Postman
2. Create a POST request to https://your-flowise-url.com/api/v1/prediction/{flow-id}
3. Set headers:
   • Content-Type: application/json
4. Send the request with the following payload:

{
  "question": "Qual a melhor estratégia para aumentar minhas vendas?",
  "overrideConfig": {
    "sessionId": "chat_12345",
    "vars": {
      "contactId": "contact_98765"
    },
    "systemMessage": "Você é um assistente.",
    "customToolName": {
      "customTool_0": "TESTE"
    },
    "customToolDesc": {
      "customTool_0": "Teste da tool 0"
    }
  },
  "history": [
    {
      "role": "user",
      "content": "Preciso aumentar minhas vendas"
    },
    {
      "role": "assistant", 
      "content": "Entendo. Vamos analisar algumas estratégias."
    }
  ]
}

5. Observe that the custom tool name and description are not being overridden

Yes, the option to allow override was already enabled in the new version.

Expected behavior
The customToolName, customToolDesc and customToolShema in overrideConfig should dynamically modify the name and description of the custom tool with the key customTool_0.

• In previous version's (2.1.3) successful override
  

Setup

• Flowise Version: 2.2.3
• Testing Method: Postman API Request
• Environment: Web-based Flowise instance

Curl Request

curl --location 'https://your-flowise-url.com/api/v1/prediction/{flow-id}' \
--header 'Content-Type: application/json' \
--data '{
  "question": "Qual a melhor estratégia para aumentar minhas vendas?",
  "overrideConfig": {
    "customToolName": {
      "customTool_0": "TESTE"
    },
    "customToolDesc": {
      "customTool_0": "Teste da tool 0"
    }
  }
}'

Additional Context

• Confirm the override mechanism worked in previous versions
• Verify if this is a breaking change in the API
• Check if the issue is specific to certain custom tool configurations

Potential Impact
This bug prevents dynamic customization of tool names and descriptions, which could affect workflow flexibility and user experience.

Proposed Solution

• Restore the previous override mechanism
• Provide clear documentation on current method for tool configuration
• Add backward compatibility for existing override methods