HighLevel’s Update Contact Field workflow action lets you write new values to standard or custom contact fields and clear values on custom fields. This article shows how to configure Update vs Clear, pick fields, use static values or tokens, update multiple fields safely, and verify results in Execution Logs.

By the end, you’ll know when to use this action versus company/custom-object alternatives, pitfalls to avoid, and how to keep contact data accurate for personalization and reporting.

What is Update Contact Field?

The Update Contact Field action changes data that lives on a contact record directly from a workflow. You can choose Action Type to either (1) update a field with a static or dynamic value or (2) clear a field’s value. The update happens at the exact step where the action runs and is visible in workflow Execution Logs.

Key Benefits of Update Contact Field

Understanding the advantages helps you decide when to use this action versus other tools (bulk edits, import, or company/object updates).

• Data accuracy: Reduce manual edits and keep contact profiles current as people move through your funnels.

• Personalization: Drive relevant messaging by filling in fields (e.g., city, segment, plan tier) used in emails, SMS, and conditions.

• Operational hygiene: Clear obsolete values so Smart Lists, filters, and reports stay trustworthy.

• Speed to action: Update multiple fields in one step for instant downstream decisioning and branching.

• Consistency: Use tokens to pull values from the contact or workflow context so updates are uniform and error-free.

Select Action Type

Start by choosing how you want the action to behave either update a field with a value or clear an existing value. The choice determines which configuration inputs appear next.

• Action Type options:

  • Update field data  write a new value.

  • Clear field data remove the stored value (custom fields only).

Update Field Data

Use this mode to overwrite a contact field’s value. You can enter a static value or insert a dynamic value using tokens.

• Select a Field (e.g., City, Phone, a custom field like Lead Source).

• Enter a Value:

  • Static value: Type a fixed string/number/date.

  • Dynamic value (token): Click the token picker and choose variables such as {{contact.email}}, {{contact.first_name}}, or date functions.

• The new value overwrites the prior value.

Clear Field Data

Use this mode to remove the stored value from a contact custom field—helpful when a value is no longer relevant or would cause logic to misfire.

• Choose Clear field data under Action Type.

• Select one or more Contact Custom Fields to clear.

• On run, the value is set to empty/NULL.

Caution: Clearing values can change segment membership and workflow conditions. Confirm the impact on Smart Lists and filters before publishing.

Use Dynamic Values (Tokens)

Tokens pull live values from the contact or workflow context, keeping updates accurate and automated.

• Insert tokens via the tag/variable icon in the value field.

• Common examples: {{contact.first_name}}, {{contact.email}}, {{contact.phone}}, custom fields like {{contact.custom.my_field}}.

• For dates, use supported date tokens or current date functions (ensure the target field is a Date type).

• Tokens resolve at runtime for the individual contact enrolled.

Update or Clear Multiple Fields

Save steps by applying several field changes in one action.

• Click Add field inside the action to include additional field rows.

• You can mix Update (with values/tokens) and Clear (custom fields) by creating separate actions if needed for clarity and auditability.

Field Type Considerations & Validation

Matching the value to the field type prevents errors and ensures reliable reporting.

• Text/Number: Provide appropriate formats; numbers accept digits only.

• Date: Use a valid date format or the date token; the system stores a proper date value.

• Dropdown/Checkbox/Radio: The value must match an existing option exactly.

• Email/Phone: Supply valid, properly formatted values.

• No creation on the fly: The action can’t create fields select fields that already exist on the contact record.

How To Set Up Update Contact Field

Follow these steps to configure the action correctly and avoid overwriting the wrong data.

Open Workflows

From the left navigation, click Automation to open the Workflows list. Select Create Workflow and choose how to start (e.g., Start from Scratch, Select a Recipe/Template, or Surfboards based workflow).

Pick Action

In the builder, click the step’s + and open the Actions drawer under Contact. Choose Update Contact Field to add the action to your workflow.

Name Action

In the action panel, enter a clear Action Name (for example, “Update contact field”). Descriptive names make it easier to find this step later in the canvas and Execution Logs.

Choose Type

Open the Action Type dropdown and select Update field data to write a value or Clear field data to remove one. Your selection controls which configuration inputs appear below.

Select Field

Use the Select Field menu to search and pick the target contact field; standard options like Business Name, City, Country, and Date of birth are listed first. If you’re updating a custom field, search by its name and then supply the value (or token) in the value box.

Frequently Asked Questions

Q. Can I update standard contact fields like Email or Phone?

Yes. Update field data supports both standard and custom contact fields.

Q. Can I clear standard fields like Email or Phone?

No. Clear field data currently supports Contact Custom Fields only.

Q. Can I update or clear multiple fields in the same action?

You can update/clear multiple fields inside one action using Add field. For clarity and logs, some teams prefer separate actions for update vs. clear.

Q. What happens if I enter the wrong format (e.g., text into a date field)?

The update may fail validation. Check the field type and use supported formats/tokens, then review Execution Logs.

Q. Do tokens work in this action?

Yes. Insert tokens (e.g., {{contact.first_name}}, custom field tokens, or date tokens) using the picker next to the value field.

Q. Does this action create a field if it doesn’t exist?

No. Create the field first in Settings → Custom Fields, then reference it here.

Q. Will clearing a value affect Smart Lists or conditions?

Yes. Clearing a value can remove contacts from lists or change workflow branches that rely on that field. Review dependencies before publishing.

Q. Can I use this in AI-triggered or company workflows?

It works in any workflow where Contact is the target record. For Company fields or custom objects, use the related actions noted above.