Notifications
Clear all
Topic starter
I'm attempting to have the agent utilize the call workflow tool, which in turn calls a workflow agent responsible for managing my Google tasks. When I execute the main agent using the test workflow button, it functions correctly. However, upon changing the status to active and sending a request for any task-related query, I encounter the error "Node cannot be used as a tool".
I'm uncertain about the reason for this, as the call workflow node is intended to be an AI agent tool.
Information on your callin.io setup
- callin.io version: 1.79.3
- Database (default: SQLite): default
- callin.io EXECUTIONS_PROCESS setting (default: own, main): default
- Running callin.io via (Docker, npm, callin.io cloud, desktop app): Railway
- Operating system: win 11
Posted : 26/02/2025 4:22 pm
I've also observed that you aren't utilizing $fromAI to have the AI generate specific queries for your sub-workflow.
Furthermore, your sub-workflow isn't receiving any specific input data.
Was this an intentional choice?
Posted : 26/02/2025 8:06 pm
Topic starter
Good day gmsalomao2, thank you for the reply. The problem is I cannot include the entire workflow or the sub-workflow because the platform indicates I'm exceeding the character limit. I might have identified the issue last night during testing; it appears to be related to the Google Tasks tool node within the sub-workflow. When I removed it and used Airtable as the task management tool in the sub-workflow, the "node cannot be used as a tool" error disappeared.
I've also tried using the sub-workflow directly with Telegram, and I'm encountering strange responses, although it functions correctly in a test environment. I'm beginning to suspect there might be a bug with the Google Tasks tool.
Posted : 27/02/2025 4:16 am