> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemtipsandtricks/widgets/advanced-input/color-picker.md).
# Color Picker
The Color Picker widget allows the user to select a color using a color picker and returns the hex color code. This hex value can then be used for other uses in the project by saving it to a field, as almost all color properties work with hex codes.
### Properties
#### General
| Property Name | Datatype | Description |
| ------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Text field | Data field, Text | Data field to store the selected color. The widget returns a hexadecimal color value. This value includes a leading number sign (#). For example: "#366dbf". |
#### Behavior
| Property Name | Datatype | Description |
| ------------------------------ | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| On change | Dropdown |
When the user selects a color one of the following events can be triggered:
Do nothing
Refresh screen
Follow exit
Execute flowchart
|
| Follow exit/ Execute flowchart | Exit/ Flowchart | The exit that should be used or the flowchart that should be triggered by the on chance action |
---
# 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.wem.io/platform/wemtipsandtricks/widgets/advanced-input/color-picker.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.
