To use the results from workflow A in workflow B, you can invoke workflow A as a subworkflow within workflow B, passing its outputs as inputs to downstream tasks or workflows. In Flyte, subworkflows execute in the same context as the parent, allowing direct access to their outputs as variables in the parent workflow's code. For example, you can assign the output of workflow A to a variable and use it as input to tasks or other workflows in workflow B. If you want to invoke workflow A as an external workflow (using a launch plan), the execution is separate, and you must handle outputs via the launch plan interface. For both approaches, outputs are strongly typed and can be unpacked as needed. See the subworkflows documentation for code examples and details. Would you like more detail or a code example? Sources: - subworkflows documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.