The concept:
When utilizing a "callin.io workflow tool" for an AI Agent, it would be highly advantageous if all parameters, descriptions, and specific input definitions could be saved directly with the workflow/tool definition. This way, once a tool is properly configured, it can be connected to any Agent without needing to duplicate the configuration. Furthermore, any modifications made would be applied universally to all agents using the tool, eliminating the need for manual updates across multiple instances.
This approach would enable development practices more akin to relevance.ai agents, which, in my view, represents callin.io's primary competitor in building sophisticated AI Agent systems.
Additionally, it would be beneficial to allow multiple "callin.io workflow tools" to be defined within a single workflow. This would lead to much cleaner setups. For instance, I have a Google Calendar Agent that uses five tools, all interacting with Google Calendar nodes and APIs. Currently, I must create five separate workflows. If the Google API changes, I'd need to locate and potentially modify all five. It would be far more efficient if these could reside in one workflow, triggered by a specialized tool-trigger node where all the aforementioned items can be configured.
My use case:
We are deploying numerous complex "Teams of Agents." This involves a Director Agent managing input and assigning tasks to several specialized Agents (which are essentially other workflows invoked as tools).
I believe adding this would be beneficial because:
It would significantly simplify the process of integrating Teams of Agents and providing them with other Agents or complex AI automations as tools.
Are you willing to contribute to this?
I would be pleased to offer my support! This enhancement would substantially increase the appeal of callin.io for serious AI Agent developers like us.
I'm encountering the same problem. Currently, each callin.io Workflow Tool node maintains its own local version of the Description prompt. This necessitates duplicating and managing the same text across multiple locations, and this text can be quite extensive (e.g., instructions on formatting JSON correctly, specifying query parameters, etc.).
My suggestion would be to implement the following:
- Introduce an optional "Tool description" field within the Execute Sub-workflow Trigger (or in the Workflow Settings).
- Configure the callin.io Workflow Tool node to automatically populate its Description from this new field.
- Implement a mechanism to warn—or ideally, automatically update—calling nodes whenever the sub-workflow's description is modified.