Many thanks @mrc , and my apologies for the delay.
The problem here is that the second tool expects as File the path inside the output of the first tool. So in the example above, the first tool should not be given path_inside.txt but instead the content of that file, which is /my/file.txt.
So in this case, the question is how to connect the standard output of the first tool (/my/file.txt) [which is saved in path_inside.txt] as input to the --in_file argument of the second tool ?
Hello @mrc, if you think there is no simple way to pass the path to an existing file written in a text file (as stdout), do you know if there would be a way to pass it in a different way ?
Again, the output of the first step is a string which is a path to an existing file, so if stdout is used, it is not the generated text file which needs to be passed, but the text string inside that text file (that string is a path).