Skip to main content

Workflow Action: Update Contact Field

The Update Contact Field workflow action lets you set or clear values in a contact’s fields automatically during workflow execution.

Updated over 2 months ago

Who This Is For / When to Use

Use this action when you need to:

  • Update contact data automatically based on triggers or conditions.

  • Clear outdated values from custom contact fields.

  • Populate fields dynamically using data from earlier workflow steps.

What the Update Contact Field Action Does

The Update Contact Field action modifies a single contact’s data during a workflow run.

You can:

  • Update field data by assigning a new value.

  • Clear field data by removing an existing value.

Each action runs in real time as the workflow progresses.

Supported Field Types and Data Sources

This action supports both static and dynamic values.

Supported field types

  • Text fields

  • Numeric fields

  • Dropdown / Select fields (no manual option ID required)

  • Monetary fields

Dynamic values

You can insert Custom Values pulled from:

  • Contact data

  • User data

  • Appointment data

  • Calendar data

  • Message data

  • Account data

Limitations and Important Notes

  • Clear Field Data applies only to custom contact fields.
    Standard fields (such as name or email) cannot be cleared.

  • Updating a field overwrites the existing value.

  • Always test workflows before publishing to avoid unintended data changes.

How to Add the Update Contact Field Action

Step 1: Create or edit a workflow

Go to Automations > Workflows, then create a new workflow or open an existing one.

Step 2: Add a trigger

Configure the workflow trigger (for example, Form Submitted).

Step 3: Add the action

Click the + icon under the trigger to add an action.

Search for Update Contact Field and select it.

Step 4: Configure the action

Action Name

Rename the action if needed.
This name only affects how it appears in the workflow builder.

Action Type

Choose one:

  • Update field data

  • Clear field data

Step 5: Update field data (optional)

  1. Click Add field.

  2. Select the contact field you want to update.

  3. Enter a value or insert a dynamic value.

Example: Updating Business Name with a static value.

To insert dynamic values, click the tag icon.

Step 6: Clear field data (optional)

Select Clear field data, then choose the custom contact field you want to clear.

This resets the field to an empty (NULL) value.

Step 7: Save and publish

  1. Click Save Action.

  2. Save the workflow.

  3. Toggle Publish when ready.

  4. Use Test Workflow to validate behavior before going live.

Common Issues and Fixes

Field did not update

  • Confirm the correct field was selected.

  • Verify dynamic values exist at runtime.

Field did not clear

  • Ensure the field is a custom contact field.

  • Standard fields cannot be cleared.

Unexpected overwrites

  • Test workflows before publishing.

  • Avoid updating critical fields unless required.

Best Practices

  • Use clear, consistent custom field names.

  • Prefer dynamic values to reduce manual data entry.

  • Test workflows before enabling them.

  • Avoid bulk updates without validation.

  • Review workflow logs regularly for accuracy.

FAQ

What does the Update Contact Field action do?

It sets a new value for a selected contact field during a workflow run, replacing the existing value.

What is the difference between Update Field Data and Clear Field Data?

Update Field Data assigns a new value.
Clear Field Data removes the existing value and sets the field to empty.

Can I clear standard contact fields like email or name?

No. Only custom contact fields can be cleared.

Can I use dynamic values instead of static text?

Yes. You can insert Custom Values from contacts, users, appointments, calendars, messages, or the account.

Which field types support dynamic values?

Numeric, dropdown/select, monetary, and standard text-based custom fields.

Can this action overwrite existing data?

Yes. Always verify field selection and values before publishing workflows.

Did this answer your question?