Right,
but if the instances of the custom node are in the same workflow, the keys are saved in the flow storage and not the custom node. A suggestion would be to be able to pass the flow id that will be saved, as this is only possible via API, and in my use case it is necessary to use the INCREMENT of storage, in which different instances of the custom node could increment the same key , as in the image. Because via API has competition problem to update the storage.
flow.flow (13.3 KB)
increment.node (9.2 KB)