> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/data/collections/field-types/text.md). # Text Fields Learn about Text fields in Noloco tables Text fields are designed to hold basic text content. They are handy for incorporating short, non-numeric, and unformatted text such as names or titles. For instance, a text field could hold a value like 'Sample Text'. ## Text Field Formats * **Single Line** Store a single line of text, like a first name, or a company name * **Long Text** Store multiple lines of text, like notes or description * **Email address** Store an email address. Input fields ensure that all values are valid email addresses, like * **IP address** Store an IP address. Input fields ensure that all values are valid IP addresses, like 192.168.1.1 * **URL** Store a URL or website such as or noloco.io. ## Use Cases Text fields are perfect for: * Names and titles * Short descriptions * Comments and notes * Contact information (when using specific formats) * Reference codes and IDs ## Best Practices * Use Single Line for short, structured text like names or codes * Use Long Text for descriptions, comments, or any multi-line content * Choose Email, IP, or URL formats when you need validation for those specific data types * Keep field names clear and descriptive to help users understand what information to enter --- # 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://guides.noloco.io/data/collections/field-types/text.md?ask=&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.