I have one workflow which calls another via the Execute Workflow node. The first workflow’s output contains binary data. How do I test the second (called) workflow with the binary data included?
IOW, how do I include binary data in the Execute Workflow trigger node’s mock output data in order to test the workflow?
Hello, you could try creating a third workflow for sending the mock output data to the second workflow. For example, manual trigger → download google drive file → call another workflow. Should work as workaround.
If I understand correctly, that wouldn’t help. I’d instead have to place that logic inside the called workflow in order to step through the flow and “see” the inputs/outputs. And then I’d have to disable or delete it after testing, which seems janky.
Can you share your workflow? You can just execute the first workflow and let the second workflow just use a set node and called by other workflow it pin the data and the build/test the second workflow.
I’m not at my computer right now to share a screenshot, but I don’t think binary data can be pinned. The problem is not calling the second workflow with binary data. The problem is having access to the binary data within the second workflow as I step through it.
To clarify a bit more, binary data can be pinned between nodes within a workflow, but I don’t see a way to pin it across workflows - i.e. to have access to the binary data within the called workflow as I step through it.
Hey @sfx, I’ve tried to reproduce your example, but I just can’t understand how you got the binary data into the “called” workflow (Execute Workflow Trigger). Maybe there’s a setting I’m missing somewhere?
I’ve attached both the calling and called workflows below. If you get a chance, I’d appreciate any info or insights you can share.
