CRM update failed: integration user can't edit the field

Updated

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

Salesforce or HubSpot turned this update down because of access. On the project, the Automations tab's Logs show a row whose Action is Update Salesforce Field or Update Hubspot Field, with an X in Success. The message in Error comes from your CRM. It says a field can't be created or updated, or that the user doesn't have enough access. Payload shows the record and every field OnRamp tried to send.

Why it happens

OnRamp updates your CRM through your organization's connected integration, as the user shown next to User: on that integration's Details tab. If that user can't edit a field OnRamp sends, or can't edit the record, your CRM rejects the update.

Fix it

  1. On the project, go to the Automations tab and select Logs. On a busy project, enter the action name in Search logs... to find the failed row.

  2. Select View in the row's Error column. Note the fields the message mentions, and find them in Payload.

  3. Go to Settings > Integrations+.

  4. Select your Salesforce or HubSpot integration. Its Details tab opens.

  5. Find the name next to User:. That's the user OnRamp updates your CRM as.

  6. In Salesforce or HubSpot, give that user edit access to those fields and to the record.

  7. On the project, fire the automation's trigger again. For example, complete the task again or change the data field again.

  8. In Logs, select Refresh to see the new row.

  9. Once the new update succeeds, select Reset automation errors to clear the red error count.

If OnRamp doesn't need to update a field, you can stop sending it instead. On the Automations tab, select the automation in the list. In its Update Salesforce field or Update Hubspot field step, select the trash icon on the field's row under Map fields to update, and then select Save. You see these controls only if you can edit the project's settings.

This change affects only this project. If the automation came from a playbook, new projects will fail the same way. To fix it at the source, see Understanding Playbook & Project Automations.

For Salesforce integrations, the integration's page may show Run Diagnostics, which runs a set of diagnostic tests on a Salesforce record you choose. See Run the Salesforce diagnostic tool.

Still stuck?

Contact support with the project's name and link, the row's Timestamp, the text from Error and Payload, and the name shown next to User:.

More in Getting Unstuck Fast