Workflow Inputs Empty on Execution (Works in Test) - callin.io AI Tool Agent Issue?

Hey there,

Since I don't have your complete setup available, I'll make an informed guess based on the error and the screenshots you've provided.

From what I can observe, the problem occurs when your main workflow invokes the cotizador sub-workflow. It functions correctly in manual test mode, but during live execution, the inputs appear empty, which is why you're encountering the Cannot read properties of undefined (reading 'toString') error.

This typically happens when the sub-workflow anticipates a value (such as patente_lead) but doesn't receive it correctly at runtime.

Potential causes include:

• The AI Agent is transmitting the data in a format that cotizador doesn't expect (perhaps as a raw string instead of an object).
• The sub-workflow call isn't mapping the inputs correctly; it might be expecting direct values but receiving nested ones.
• Or, one of the fields is being passed as null or undefined, and your flow attempts to perform a .toString() operation on it without prior validation.

Here’s what I would suggest trying:

1. Execute the flow in debug mode and examine the data being passed just before the sub-workflow is called.
2. Verify that all inputs expected by cotizador are indeed present in the payload.
3. If necessary, utilize a Set or Function node to restructure the data before sending it to the sub-workflow.

If you could share the actual JSON originating from the AI Agent or demonstrate your sub-workflow node's configuration, I can assist further in refining it.

Hope this helps!

– Dandy

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