Use case:
I have a workflow with two paths (Website Provided / No Website). Both paths gather and normalize company data using Custom Code steps with identical output schemas. I want to use that finalized data outside the Paths step to create a Salesforce Account and Contact once — instead of duplicating those steps in every path.
Requested behavior:
When all branches of a Paths step end with a Custom Code step sharing the same output schema, that output should be accessible downstream in the parent thread — the same way resource type outputs already aggregate.
Impact: Reduces step count, eliminates duplication, and makes workflows significantly easier to maintain.