Hi,
I am working on a workflow which allows backing up and transferring workflows or an entire workspace.
Upon assessing the results I noticed that when a remote workflow was called but saved with the data, that data is saved in a sub-folder called “.artifacts” in addition to the port_# sub-folder of a node.
As follows the screenshot of the ex- and then reimported workflow:
Sharing those workflows could cause unintentional data leaks, though.
Best
Mike
Hi @mwiegand,
Those I/O JSONs are not port data but the configuration data which are used as the example request/response body when you deploy the workflow as a service.
If you clear the JSON structure in the JSON container I/O and save the workflow, you will see that the these JSON files nder .artifacts will also get cleared. So, there is no potential data leak since user uses the example JSON strcture as the node configuration intentionally and when they save and export the workflow, they know that the nodes’ configuraitons are also saved and exported with the workflow. We can make this more clear in the node description (that the JSON example in the node dialog will be exposed to the workflow service users).