Hey do you still need help with this?

Kindly update your callin.io version to 1.80.5. This addresses a known bug that has since been resolved. If this response resolves your query, pleas...

You all are amazing!!! That was incredibly fast! Thank you It's no surprise that callin.io is so effective and leads the way compared to othe...

I believe this might be a bug. Could you please try utilizing $fromAI in all those fields instead of allowing the AI to define them? Refer to the ...

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 ...

Hello, I've simplified your workflow for quick testing and managed to get it working. Please review it below: image821×452 15.3 KB This ca...

Hello! Great news! Our team is actively working on this. image665×212 9.55 KB

I've constructed the workflow from scratch and streamlined it further. The issue persists. version 1.80.3 image1259×848 64.6 KB

I've managed to replicate the issue on my end: image1081×389 15.2 KB This behavior is consistent across the following versions: 1.80.3 1.79.3 ...

Consolidate all connections within a single branch, rather than segmenting them. Like this: The "Edit Fields" node facilitates passing previou...

In callin.io, multi-branch workflows process sequentially from top to bottom. This means a branch positioned higher will execute before one below it. ...

Try aggregating the items. Let me know how it goes. . If my reply answers your question, please remember to mark it as a solution.

Currently, we have limited options for that type of interaction with AI Agents. This is a rather intricate task, but scrapers employ certain techniq...

Hello, Your tools seem to be missing descriptions for the $fromAI function. You need to specify what you want for each field. Here's an example: {...

This is all the information I could retrieve from your code. Could you please share the specific section that is causing the error? image1572×568 57...