Automation Custom Fields Are Not Updating: How to Diagnose the Problem
When automation custom fields are not updating, the workflow runs but the field stays empty or keeps its old value. The cause is in the field mapping, the source data, the field type or the action configuration. Trace the value from the source through the automation to the CRM record to find where it drops.
Table of Contents
- 01.The field update flow you are debugging
- 02.What to check first
- 03.Source data and empty values
- 04.Field mapping and field type
- 05.Contact vs opportunity fields
- 06.Action configuration and permissions
- 07.How to test it
The field update flow you are debugging
A custom field update moves a value from a source into a CRM field. The source value exists, the automation reads it, the field mapping connects source to destination, the workflow action runs and the CRM record updates. If any step fails, the field stays empty or unchanged. Trace the value through each step to find where it stops.
| Step | What happens | Where it can break |
|---|---|---|
| 1. Source value | Value exists in source field | Source field empty |
| 2. Automation reads it | Workflow captures the value | Variable not mapped |
| 3. Field mapping | Source connected to destination | Wrong field mapped |
| 4. Action runs | Update action executes | Action misconfigured or skipped |
| 5. CRM record updates | Field value written | Field type mismatch, permissions |
What to check first
- Confirm the source field actually has a value for the affected record.
- Check the field mapping from source to destination custom field.
- Confirm the field type of the destination matches the value being written.
- Check whether the update action ran or was skipped.
- Confirm the field is on the right record type, contact or opportunity.
Source data and empty values
The update can only write a value that exists. If the source field is empty, the destination stays empty. Check the source record and confirm the value is present before the update action runs. A common variant is the source field being set after the workflow reads it, so the action writes an empty value. Confirm the timing of when the source value becomes available relative to the update action.
Field mapping and field type
The mapping connects a source field to a destination custom field. If the mapping points to the wrong destination, the right field never updates. If the destination field type does not match the value, the update may fail silently or write an unexpected value. A number field will not accept text, a date field needs a date format and a single-select field needs an existing option. Confirm the mapping and the field type match the value being written.
Contact vs opportunity fields
Custom fields live on a record type. A contact field is not the same as an opportunity field. If the workflow updates a contact field but the value is on the opportunity, or vice versa, the field appears not to update. Confirm which record type the field belongs to and that the update action targets the right record. Updating the wrong record type is covered in the guide on automation updating the wrong CRM record.
Action configuration and permissions
The update action has to run and has to have permission to write the field. Check whether the action ran or was skipped by a condition. Confirm the action targets the correct field and record. Permissions can also block field updates. If the connected account or user lacks permission to edit that field, the update fails. Some fields are locked or restricted by role, so confirm the account running the workflow can edit the destination field.
How to test it
- 1.Find the record with the field that did not update.
- 2.Confirm the source field has a value for that record.
- 3.Check the field mapping from source to destination.
- 4.Confirm the destination field type matches the value.
- 5.Check whether the update action ran or was skipped.
- 6.Confirm the field is on the right record type and the account can edit it.
Frequently Asked Questions
Why is my automation not updating custom fields in my CRM?
The source value may be empty, the field mapping may point to the wrong destination, the field type may not match the value or the update action may be skipped. Trace the value from the source through the mapping to the record.
How do I fix automation custom fields that are not updating?
Confirm the source field has a value, check the mapping to the destination field, match the field type to the value and confirm the update action runs and has permission to edit the field on the right record type.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Automation Is Updating the Wrong CRM Record: How to Diagnose Record Matching Problems
The wrong record updates when the match finds a duplicate or the lookup returns multiple results. Reliable identification has to happen before the update action runs.
Webhook Data Goes Into the Wrong Field: How to Fix Mapping Problems
Wrong field mapping happens when the key does not match the payload or the data type does not match the destination. Capture the actual payload before changing the mapping.
Automation Is Overwriting CRM Data: How to Find the Workflow Causing It
Overwrites are caused by the last process to run. Trace the field history to find the last writer before changing any individual workflow.