> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/text-file-input-cp/select-an-engine-text-file-input/using-text-file-input-on-pentaho-engine-cp/options-text-file-input-reuse/file-tab-text-file-input-pentaho-engine/accept-file-names-text-file-input-kettle.md).

# Accept file names

![Accept filenames from previous steps](https://3411831820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAYwCj9fPr1B2pjC11IOQ%2Fuploads%2Fgit-blob-767ef055768d17a4b212fb2240d921dbb6b4bc32%2FPDI_TextFileInput_Dialog_AcceptFilenamesFromPreviousStep.png?alt=media)

You can specify your file name and pass it to the input step, which allows the file name to come from any source, such as a text file or database table.

| Option                                     | Description                                                                        |
| ------------------------------------------ | ---------------------------------------------------------------------------------- |
| **Accept filenames from previous step**    | Select to get file names from previous steps.                                      |
| **Pass through fields from previous step** | Select to get field information from previous steps.                               |
| **Step to read file names from**           | Enter the name of the step from which to read the file names.                      |
| **Field in the input to use as filename**  | Enter the name of the field in the input step to determine which file name to use. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/text-file-input-cp/select-an-engine-text-file-input/using-text-file-input-on-pentaho-engine-cp/options-text-file-input-reuse/file-tab-text-file-input-pentaho-engine/accept-file-names-text-file-input-kettle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.