Select Input Folder:
Select Input Folder helps you pass a folder location to another node in your workflow. It offers the current input subfolders as choices, then builds a text path for the folder you select. This is useful when another node needs a folder location: you can choose from the available folders instead of typing the path yourself. The node only constructs the path; it does not open the folder, check its contents, or load images.
Select Input Folder Input Parameters:
folder
Choose the folder to represent in the resulting path. The available options are . and the input subfolders returned when the node’s choices are populated. Choosing . represents the base input location when the base path is included. There is no numeric minimum or maximum, and the source does not specify a default folder choice. The selected text becomes the final component of the path.
with_base_path
Choose whether to put input at the start of the resulting path. This Boolean setting defaults to True. With True, selecting a folder such as portraits produces input/portraits on systems that use forward slashes; with False, it produces portraits. The path separator may differ by operating system. The available values are True and False; a numeric minimum and maximum do not apply.
Select Input Folder Output Parameters:
folder
A string containing the constructed folder path. It combines the selected folder with input when with_base_path is True; otherwise, it returns the selected folder as a relative path. For example, selecting portraits with the default setting gives input/portraits on systems that use forward slashes. This value is a location for another node to use, not a list of files or confirmation that the folder exists.
Select Input Folder Usage Tips:
- Leave
with_base_pathset toTruewhen the next node expects a path beginning withinput. Turn it off when the next node expects just the selected subfolder name or another relative path. - Select
.when you mean the base input location rather than a named subfolder. Check whether the receiving node accepts a path such asinput/.or.; this node does not simplify or validate it. - Check the receiving node’s path requirements before connecting the output. Select Input Folder returns text and does not itself load images or verify access to the folder.
- If a newly created subfolder is not offered in the menu, refresh the node’s available choices so the input subfolders can be listed again.
Select Input Folder Common Errors and Solutions:
Selected folder is not available in the menu
- Explanation: The choices come from the input subfolders available when the node’s menu is populated. A folder created afterward may not appear immediately.
- Solution: Confirm that the folder is an input subfolder, then refresh the node or workflow interface to reload the choices.
Downstream node reports that the folder cannot be found
- Explanation: Select Input Folder builds a path but does not check whether another node can find it. The receiving node may expect a different starting location or may be given a folder that has been moved or removed. This is a possible downstream error, not an error message defined by Select Input Folder.
- Solution: Check that the folder still exists and set
with_base_pathto match the path format the receiving node expects.
Downstream node reports permission denied
- Explanation: A node that tries to read the selected location may be unable to access it. Select Input Folder itself does not read the folder or define this error message.
- Solution: Check that your application can access the folder, or select an accessible input subfolder.
TypeError while joining the path
- Explanation: The node passes the folder value to Python’s path-joining function, which expects a path-compatible value. This could occur if an invalid value is supplied outside the normal folder menu; the source does not specify one exact error-message string.
- Solution: Re-select a listed folder option and make sure any workflow mechanism supplying this value passes folder text rather than another data type.
