Skip to content
Troubleshooting a c...
 
Notifications
Clear all

Troubleshooting a callin.io workflow tool error

10 Posts
3 Users
0 Reactions
4 Views
b-ub
 b-ub
(@b-ub)
Posts: 5
Active Member
Topic starter
 

Hello everyone,

My AI agent can successfully trigger the "callin.io Workflow Tool," but I'm encountering an error. The attached screenshots show an agent configured to generate an image. This functionality works when triggered via Telegram, but not when using the AI tool.

Here are my current settings:

  • Input: The agent is set to utilize the tool.
  • Tool: Source is set to "Database," and the correct workflow is selected.
  • Trigger: Configured as "Executed by another Workflow" with "Accept all data" enabled.
  • Naming: Both the request and nodes are named correctly.
  • Version: I am using the cloud version.

Does anyone have any insights into what might be causing this issue? Any help would be greatly appreciated!

 
Posted : 22/03/2025 7:46 pm
solomon
(@solomon)
Posts: 78
Trusted Member
 

It's a good practice to define the input your sub-workflow will accept. Selecting “Accept all data” leaves it open to various structures, which can lead to errors.

Try configuring it like this:

AI Agent

Subworkflow

Notice how I've restricted the data type accepted by the sub-workflow.
Also, observe the $fromAI function used within the tool.

:point_right:

If this response resolves your query, please consider marking it as a solution.

 
Posted : 22/03/2025 9:33 pm
b-ub
 b-ub
(@b-ub)
Posts: 5
Active Member
Topic starter
 

Hi Solomon,
Thanks so much for your support! Unfortunately, the sub-workflow still isn’t being triggered. Any other idea what might be causing it?

Could you offer any other suggestions on why the sub-workflow might not be triggering? I appreciate your help!

 
Posted : 24/03/2025 6:15 am
solomon
(@solomon)
Posts: 78
Trusted Member
 

Hello,

I noticed you're not currently using an expression in that field, but rather fixed text.

To switch to using an expression, hover over the text field. You should see two small tabs appear:

  • Fixed
  • Expression

Click on "Expression" to enable it.

 
Posted : 24/03/2025 11:05 am
b-ub
 b-ub
(@b-ub)
Posts: 5
Active Member
Topic starter
 

It’s still not working, unfortunately – but I think we’re on the right track!

:blush:

Do you have another idea we could try? Thanks a lot!

 
Posted : 24/03/2025 1:33 pm
solomon
(@solomon)
Posts: 78
Trusted Member
 

The error message indicates that the workflow ran twice, once for each item. However, on the second item, the Telegram Trigger did not activate.

This suggests that you are sending more items downstream than the Telegram Trigger is actually initiating.

 
Posted : 24/03/2025 2:08 pm
b-ub
 b-ub
(@b-ub)
Posts: 5
Active Member
Topic starter
 

The multiple trigger issue is resolved – great!

But the tool is still not being triggered. Do you have any other suggestions we could try? Thanks a lot!

 
Posted : 24/03/2025 3:23 pm
solomon
(@solomon)
Posts: 78
Trusted Member
 

Could you please examine the execution that resulted in the error and pinpoint its location?

You'll need to navigate into the subworkflow and review its executions.

 
Posted : 24/03/2025 8:12 pm
b-ub
 b-ub
(@b-ub)
Posts: 5
Active Member
Topic starter
 

Thanks to your last message, I found and fixed the issue. Really appreciate it!

 
Posted : 26/03/2025 6:55 am
system
(@system)
Posts: 332
Reputable Member
 

This discussion was automatically closed 7 days following the last response. New replies are no longer permitted.

 
Posted : 02/04/2025 6:55 am
Share: