Subflow Dependency and Token Handling Issues in Marketplace Workflows

Issue:
Both main workflows and subflows are visible separately in the marketplace. When a main workflow depends on a subflow, users must discover and purchase both the main workflow and the required subworkflow. This creates a major usability issue. In a marketplace with hundreds or thousands of workflows, users cannot easily identify which subworkflow is required for a specific main workflow, making discovery and correct purchase impractical.

Additionally, workflows that use subflows require separate token loading for both the main workflow and the subworkflow. This adds unnecessary friction and confusion for users, since they must manage tokens across multiple dependent workflows instead of handling the execution as a single unit.

Expected Result:
Subflows should be treated as internal dependencies of the main workflow, not separate items users must manually find and purchase. The platform should:

• Bundle subflows automatically with the main workflow, so users only purchase the main workflow.

• Hide subflows from the marketplace or mark them as internal dependencies.

• Automatically install required subflows when the main workflow is purchased.

For token handling, the platform should implement a single token loading mechanism. When a user runs or purchases a main workflow, the system should automatically calculate the total token cost including all dependent subflows and allow the user to load tokens once for the entire execution. This ensures a smoother and more intuitive user experience.