CRM update failed: mapped fields not found
Last updated: October 2, 2026
Applies to: Super Admins, Creators, and Integrators, with Salesforce or HubSpot connected
Project automations are available when they're turned on for your organization. If you don't see an Automations tab on your projects, contact your OnRamp team.
This CRM update stopped because OnRamp couldn't find the fields it maps to. In the project's Logs, the Update Salesforce Field or Update Hubspot Field row has an X in Success, and Payload shows only {}. Error includes No data found to update. It then lists each skipped field by its API name, with the reason not in the CRM field list.
Why it happens
Each row under Map fields to update sends an OnRamp value to a CRM field: a Salesforce field or a HubSpot property. Before it updates the record, OnRamp looks for each mapped field in its copy of the object's field list. If a field is missing, OnRamp refreshes the list from your CRM once and looks again. Fields that are still missing are skipped. When every field is skipped, there's nothing left to send.
A field goes missing when it's deleted or its API name changes in your CRM. It also goes missing when the action's record is changed to another type, such as from an Opportunity to an Account. The mapping rows keep the old type's fields.
Sometimes the reason in Error is mapped value is empty instead. That means OnRamp found the field but had no value to send, such as an unanswered subtask. Add that value in OnRamp, and then repeat the event.
Fix it
- In Logs, select View in the Error column, and note the fields it lists.
- Select the automation in the list. It opens in Workflow.
- Select the Update Salesforce field or Update Hubspot field step.
- Next to Salesforce Object Entity or Hubspot Object Entity, select the refresh button. It reloads OnRamp's copy of the object's fields and changes nothing in your CRM.
- Under Map fields to update, find the rows for those fields. A row whose field is missing has no field selected. The list shows field labels, which can differ from the API names in Error.
- In each of those rows, select a field under Update this field, or remove the row with its trash button.
- Select Save.
- Repeat the event on the project. Then, in Logs, select Refresh to see the new row.
If a field still isn't in the list after the refresh, check in Salesforce or HubSpot that it exists on that object. Also check that the user OnRamp connects as can see it.
If only some mapped fields are missing, the update still runs for the rest. See Project automation succeeded, but a CRM field didn't change.
Still stuck?
Contact support with the project's name and link, the row's Timestamp, and the text from Error. Include the CRM object the action updates and the API names of the missing fields.