> 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/couchdb-input/options.md).

# Options

Enter the following information in the transformation step fields:

| Option                      | Description                                                                                                                                                                                                                           |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Step Name**               | Specify the unique name of the CouchDB Input step on the canvas. You can customize the name or leave it as the default.                                                                                                               |
| **Host name or IP**         | Specify the host name for the connection to your database.                                                                                                                                                                            |
| **Port**                    | Specify the port number for the connection to your database.                                                                                                                                                                          |
| **Database**                | Specify the name of the incoming database.                                                                                                                                                                                            |
| **Design document**         | Identify the source design document. Design documents are a special type of CouchDB document that contains application code. See [CouchDB Design Documents](http://guide.couchdb.org/editions/1/en/design.html) for more information. |
| **View name**               | Identify the source CouchDB view. See [CouchDB Views](http://guide.couchdb.org/editions/1/en/views.html#views+) for more information.                                                                                                 |
| **Authentication user**     | Specify the username required to access the database.                                                                                                                                                                                 |
| **Authentication password** | Specify the password required to access the database.                                                                                                                                                                                 |


---

# 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/couchdb-input/options.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.