> For the complete documentation index, see [llms.txt](https://hubflo.gitbook.io/get-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hubflo.gitbook.io/get-started/more/setup-custom-fields.md).
# Setup custom fields
Custom fields provide a unique flexibility to enrich your information on contacts, companies, projects, and tasks, making them more detailed and tailored to your specific needs!
In this article, you will understand how to create and use custom fields on Hubflo!
Let's go 👇
***
## 1 - Create custom fields
* From your settings, go to the 'Custom Fields' section, then choose the category: contacts, projects, notes, or tasks.
* Select '+ New Custom Field', then give it a title and choose its type: text, integer or decimal number, date, or list.
***
## 2 - Using my custom fields
Here, we have added the custom field: *Secondary email address*.
Thanks to this custom field, you can now add a second email address to your contacts!
💡 You can also add other custom fields to your contacts such as :
* The job title
* The language used by the contact in the case of an international company 🙂
Or any other element that resonates with your needs!
---
# 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://hubflo.gitbook.io/get-started/more/setup-custom-fields.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.
