> For the complete documentation index, see [llms.txt](https://docs.tomorrowx.com/cap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomorrowx.com/cap/product-reference/administration-functions/input-adaptors.md).
# Input Adaptors
Input adaptors are used to define how a server receives input. Examples are CSV files, HTTP or XML. Setting up input adaptors is an administrative function.
Input Adaptor
To set up a new input adaptor, you will need to obtain relevant details from the programmer who wrote the code for the adaptor. The following section details the individual settings.
The class name is the fully qualified class name of the adaptor. It must exist in the classpath of the server that is going to use it.
Input adaptors come in two forms: test and production.
Test adaptors only work from file data that is pushed to the adaptor from the console.
Production adaptors either wait or poll for data. An HTTP request adaptor would wait for data, whereas an adaptor that reads files from a directory would be polling.
The optional parameter label denotes the lead text for a configuration field available when configurations are defined. This allows you to specify custom data to pass to the adaptor when it is loaded *(for example a directory or file name).*
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.tomorrowx.com/cap/product-reference/administration-functions/input-adaptors.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.