> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/answers/answer-types/creating-new-type.md).

# Creating New Type

While offering a wide range of answer types there are times when you might need to build your own answer type to meet a specific business case. ngSurvey allows your to create new answer types with or without programming knowledge.

You may create following types of answer types.

* [Custom fields](/form-management/form-designer/answers/answer-types/creating-new-type/custom-validation-code.md) with your own custom javascript validation code.
* [Data source lists of items](/form-management/form-designer/answers/answer-types/creating-new-type/lists.md) to create lists that are build using a collection of text / value based items. Those lists can be build either from scratch or you may re-use existing data from a JSON REST API endpoint or from a Microsoft SQL Server database table.
* [Widgets](/form-management/form-designer/answers/answer-types/creating-new-type/widget.md) to create a powerful javascript, html and css based answer types. Using widgets you may develop almost any kind of functionality that you would miss in ngSurvey to collect data.

## ➕ Adding a new answer type

To create a new answer type you may click on the **+** icon to open the answer editing interface to add your type.

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBzXkzKdmRcF4VDpqgo%2F-MBzXqs2qPjFomvfnWLl%2Fimage.png?alt=media\&token=e7916c27-f3fd-4dff-85eb-30bfbca3eae0)

{% hint style="info" %}
New answer types can only be used and seen by the account that creates them.
{% endhint %}


---

# 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.ngsurvey.com/form-management/form-designer/answers/answer-types/creating-new-type.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.