> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/workflows/creating-workflows/configuring-thinklets/update-custom-fields-thinklet.md).
# Update custom fields thinklet
The **Update custom fields** thinklet writes values to existing manual custom fields—**Device** or **User** object. Refer to [Custom fields management](/user-guide/administration/content-management/custom-fields-management.md) to learn how to create and configure manual custom fields.
Use this thinklet to store values in custom fields from workflow executions, as the result of a decision or a user response, for downstream use and automations:
* Update metadata such as compliance, onboarding, or asset tracking.
* Update Nexthink dashboards or investigations.
* Trigger follow-up workflows based on updated custom field values.
{% hint style="info" %}
Refer to [Creating workflows](/user-guide/workflows/creating-workflows.md#updating-custom-fields-in-workflows-for-downstream-use) for use case examples of **Update custom fields** thinklets.
{% endhint %}
## Configuring the Update custom fields thinklet
Fill in the following configuration fields:
* **Name**: Enter a unique name for the thinklet.
* **ID**: Auto-generated based on the name.
* **Description (optional)**: Describe the thinklet purpose to facilitate collaboration.
* **Object**: Select either **Device** or **User**. The object defines which custom fields are available.
* To update both **Device** and **User** objects, chain multiple thinklets.
* **Select custom field**: Choose one or more manual custom fields (up to 10) to update. Choose how to assign the value:
* **Custom value**: Enter a fixed value.
* **Device** or **User** properties, such as **CPU** or **Entity**.
* **Thinklet**: Use output from a previous thinklet. For example, a campaign response.
{% hint style="warning" %}
Custom field updates are asynchronous and may take up to 5 minutes. If later workflow steps need to read the updated values, add a **Wait** thinklet.
You can update up to 10 custom fields per thinklet for a specific object. Check the status of the update result from the [workflow execution timeline](/user-guide/workflows/monitoring-workflows-dashboard/troubleshooting-workflows.md#update-custom-fields).
{% 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.nexthink.com/user-guide/workflows/creating-workflows/configuring-thinklets/update-custom-fields-thinklet.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.
