> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Update Field

> Set or clear field values on a contact record as they pass through a workflow.

The Update Field node modifies a field value on the contact record during workflow progression. Use it to set flags, update lifecycle stages, clear stale data, or write any value that downstream nodes or external systems depend on.

## Configuration

### Actions

| Action          | Description                                                                                                                                                            |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Set value**   | Assigns a new value to the selected field. You can enter a fixed value, or type `/` to open the command menu and insert liquid expressions, contact fields, or tokens. |
| **Clear value** | Removes any existing value stored in the selected field, leaving it empty.                                                                                             |

<Info>
  Text inputs in this node support [Liquid templating](/product-docs/liquid/overview). Type `/` in any text field to open the command menu and choose from **Add liquid**, **Add a field**, or **Add a token** to insert dynamic values.
</Info>

### Overwrite toggle

By default, existing field values are preserved. When the **Overwrite existing values** toggle is enabled, any existing value is replaced with the new one you set.

| Toggle state      | Behavior                                                                              |
| ----------------- | ------------------------------------------------------------------------------------- |
| **Off** (default) | If the field already has a value, the node is skipped. Only empty fields are updated. |
| **On**            | The field is always updated, replacing any existing value.                            |

<Info>
  The **Clear value** action always removes the current value regardless of the overwrite toggle, since clearing is inherently a destructive operation.
</Info>

## Behavior

* The node executes once per contact as they pass through.
* The field is updated on the contact record before the contact advances to the next node.
* Downstream nodes (branches, emails, webhooks) will see the updated value immediately.

## Use cases

* **Set lifecycle stage** — update a `lead_stage` field to "MQL" when a contact reaches a qualifying step in the workflow
* **Reset tracking fields** — clear a `last_clicked_date` field at the start of a sequence so only new click events are captured
* **Flag workflow participation** — set a `in_nurture_workflow` field to `true` at the start and clear it at the end, so other workflows or branches can check whether the contact is currently in this sequence
* **Prepare data for branching** — set a standardized value before a [Field Branch](/product-docs/workflows/nodes/field-branch) node to ensure clean routing