The answer is yes, maybe, no with the former being closer.
Here is what I heard.
1. I have a "pattern" of named documents, such as INV-1 through INV-150
2. I want in a UI the ability to select folders for Source and Target
3. I want to be able to input "some" type of text
4. I want the flow to be able to understand what I typed in #3 as a "pattern" not a specific file name, and find all the matching ones, however in this case the pattern could be using numbers (sequential, maybe not???) so we cannot simply look for INV* because you could have INV_1 through INV_2599 but I only want to go from 1-150 (as in your example)
The sticking point, but not the hinderance is the exact patterns of files you would need to do. This is critical at the beginning, otherwise we solve for 1-150 and your flow doesn't really work.
Image that your pattern was always something like
INV_#####
TEST_#####
FOO_####
Then it is easy, because you can simply allow the user to type in the text part INV_ and then put the range of numbers 1 and 150 and the flow dynamically builds the name at run time.
But if the pattern is actually not that simple it requires much more work.
Can you please verify if my assumptions are accurate and also come up with some more specific scenarios for filenames so that a real applicable answer can be formulated.
Cheers!
If this helps you, please Mark as such and maybe a like :-)