Skip to content
Adding 'description...
 
Notifications
Clear all

Adding 'description' to Input fields for 'When Executed by Another Workflow' to inherit descriptions when using the workflow as an AI Agent tool with callin.io workflow tool

2 Posts
2 Users
0 Reactions
3 Views
tresorama
(@tresorama)
Posts: 1
New Member
Topic starter
 

The concept is:

Consider the following workflow, featuring an AI Agent node that utilizes another callin.io workflow as a tool via the Call n8n workflow tool.

Now, it's necessary to add fields for descriptions within this workflow.

It would be preferable to define these descriptions within the invoked workflow (the Tool Workflow).

Feature Description

Details:

  • When Executed by Another Workflow node: add description within the Input schema Fields.
  • Call n8n workflow tool node: introduce the ability to inherit or overwrite the description.
  • Call n8n workflow tool node: if inherit is selected, display the inherited description in the UI.

My use case:

AI Agent's tool reusability.

I think it would be beneficial to add this because:

  • Improved separation of concerns: Currently, the input schema needs to be edited at the consumer level (Parent Workflow) as well as the server level (Tool Workflow). This is akin to the API being split between server and client, when it should reside solely on the server (like MCP Servers).
  • Reduced workflow maintenance: Presently, when a description changes due to API modifications, you must update the description in every Parent Workflow that uses the other workflow as a tool. This can involve a significant number of workflows.

Are you willing to work on this?

No, but I can contribute to the DX discussion. I am on GitHub (tresorama).

 
Posted : 15/04/2025 12:46 am
jimmytacks
(@jimmytacks)
Posts: 2
New Member
 

This is the same issue as: Improve AI Agent ‘callin.io workflow tool’ - Feature Requests - callin.io Community

My comment on that thread was:

I have the same issue. Right now every Call callin.io Workflow Tool node keeps its own local copy of the Description prompt, so we have to maintain the same text in several places. And that text can be quite substantial (how to format JSON correctly, what parameters to pass in query etc.).

I’d suggest doing something like:

  1. Add an optional “Tool description” field to the Execute Sub-workflow Trigger (or Workflow Settings).
  2. Make the Call callin.io Workflow Tool node pre-populate its Description from that field
  3. Warn—or ideally auto-update—caller nodes if the sub-workflow’s description changes later.
 
Posted : 24/06/2025 1:59 pm
Share: