Concerning the problem of saving the workflow containing child nodes.

[807502278]

It is recommended to include the child nodes in the saved workflow. Otherwise, when sharing a workflow with child nodes, you would have to look for the json files in the subnodes to package them, and then others would have to manually place these json files into the subnodes. Or, could we make an advanced save and load option to automatically package and unpackage the zip?

[vivax3794]

I have thought about this as well. And not quite sure how I want to attack it either, different save options do seem like the best way to go.

The question then becomes how editing these embedded workflows will work, just automatically unpacking them into the subnodes folder might not be desirable.

Inline editing is a request I have gotten from a few people so that would be a good option, although I am not sure how to best tackle that atm.

[807502278]

This function of the main body is the same as that of the final child node. Although it is very difficult to use, could its save be referred to?
Of course, it's just reference save. I think the subnodes folder is quite useful