Project automation succeeded, but a CRM field didn't change

Updated

Applies to: Super Admins, Creators and Integrators, with Salesforce or HubSpot connected

The log shows a check mark for the update, but a Salesforce field or HubSpot property didn't get the value you expected. The row's Payload shows which fields OnRamp left out or shortened, and why. People with the Contributor or Collaborator seat license don't see a project's Automations tab.

Why it happens

An Update Salesforce field or Update Hubspot field action can succeed even when OnRamp leaves out a mapped field or shortens its value. The row gets a check mark when at least one mapped field is still sent and Salesforce or HubSpot accepts the update. The row's Payload lists the affected fields by their CRM API name, not their label:

  • skipped_fields: OnRamp didn't send the field, so the CRM kept its old value. The reason is not in the CRM field list when OnRamp couldn't find the field on the CRM object. It's mapped value is empty when the OnRamp value had nothing in it.

  • truncated_fields: the value was longer than the CRM field allows. OnRamp sent the first max_length characters, and original_length is the full length. mapped_from names the OnRamp source the value came from, such as a data field's name or a project field's label.

OnRamp shortens only free-text values headed for a free-text field. Other values that are too long fail the action instead, so the row shows an X, not a check mark. If that's what you see, follow CRM update failed: the CRM rejected the value.

If every mapped field is skipped, there's nothing left to send. The action fails with a No data found to update on <object>: ... error instead. In that case, follow CRM update failed: mapped fields not found.

Fix it

  1. On the project's Automations tab, select Logs.

  2. Find the row whose Action is Update Salesforce Field or Update Hubspot Field for the event.

  3. In Payload, select View, and find your field in skipped_fields or truncated_fields.

  4. Select Workflow, and then select the automation.

  5. Select its Update Salesforce field or Update Hubspot field step.

  6. Fix the field based on what you found:

    • not in the CRM field list: in Salesforce or HubSpot, check that the field still exists on that object. Then select the refresh button next to Salesforce Object Entity or Hubspot Object Entity, and select the field again under Update this field.

    • mapped value is empty: fill in the value it's mapped from, such as a data field on the project's Data Fields tab. Or select a different value under With this data. On a Subtask completed trigger, only subtasks answered before the triggering one have a value.

    • truncated_fields: use mapped_from to find the value under With this data. In Salesforce or HubSpot, let the field hold a longer value, or select a shorter value under With this data.

  7. If you changed the mapping, select Save. Only people who can edit the project's settings see Save. For everyone else, the automation is read-only.

  8. Repeat the event on the project. Then, in Logs, select Refresh.

If your field is in neither list, look for it in the fields list under record. That's the value OnRamp sent, to the record whose id is under record. Check that record in Salesforce or HubSpot.

OnRamp also leaves out a mapped field when it would only send a synced value back to the same CRM record. That field doesn't appear in skipped_fields, truncated_fields or fields. If every mapping is left out this way, the action writes no row in Logs.

Still stuck?

Contact support with the project's name and link, the automation's trigger and action, the field's API name, the row's Timestamp, and the text from Payload.

More in Getting Unstuck Fast