Mapping Error in Email Waterfall Output for Salesforce Record Update

Lean Bandioque · 2025-07-01 11:32:41.752413+00

I am encountering a mapping error on the email waterfall output when attempting to update a record in Salesforce. Could you please assist me in resolving this issue? Thank you for your time and consideration.

Mapping Error in Email Waterfall Output for Salesforce Record Update | Clay

7 comments

· Sorted by Oldest

Clay
APP
·
·
When encountering a mapping error with email waterfall output to Salesforce, check these key areas: 1. Verify field type compatibility between Clay and Salesforce - ensure your email field types match exactly. 2. Check if you've enabled "Remove Blank Values" in your Update Record action. If set to false, blank values might be overwriting existing data. 3. Review your field mapping to ensure you're correctly referencing the waterfall output column. If you could share the specific JSON error message you're receiving, I can provide more targeted troubleshooting.
Sources: Salesforce integration overview | Documentation | Clay University Waterfall | Documentation | Clay University Salesforce Integration Guide Salesforce integration overview | Documentation | Clay University
Lean Bandioque
·
·
This is the error "Settings contains deleted column for "object_fields|Email"input"
Clay
APP
·
·
This error occurs when you're trying to map to an Email field that was previously configured but has been deleted or renamed in your Salesforce Update Record action. To fix this: 1. Open your Salesforce Update Record action 2. Check the "Object Fields" section 3. Remove the deleted Email field mapping 4. Re-add the correct Email field from your Salesforce object 5. Ensure field types match between Clay and Salesforce If you're still having issues, please share the complete JSON error message so I can provide more specific troubleshooting.
Sources: Update Record with Salesforce Salesforce integration overview | Documentation | Clay University Salesforce integration overview | Documentation | Clay University
Lean Bandioque
·
·
https://app.clay.com/workspaces/530147/workbooks/wb_0syo2ri5Rc7AeHuvcND/tables/t_0syprx2FVhF27au5gmN/views/gv_0syprx2mTRbKpy3z7Dx
Mark (Clay)
·
·
Lean, thanks for sharing this. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
1
Mark (Clay)
·
·
Looks like we've repaired this issue, and you should not see this if you create a new column that uses the waterfall as an input. Could you have a look, and let me know if you still hit a roadblock?
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.

Clay
APP
·
·
When encountering a mapping error with email waterfall output to Salesforce, check these key areas: 1. Verify field type compatibility between Clay and Salesforce - ensure your email field types match exactly. 2. Check if you've enabled "Remove Blank Values" in your Update Record action. If set to false, blank values might be overwriting existing data. 3. Review your field mapping to ensure you're correctly referencing the waterfall output column. If you could share the specific JSON error message you're receiving, I can provide more targeted troubleshooting.
Sources: Salesforce integration overview | Documentation | Clay University Waterfall | Documentation | Clay University Salesforce Integration Guide Salesforce integration overview | Documentation | Clay University
Lean Bandioque
·
·
This is the error "Settings contains deleted column for "object_fields|Email"input"
Clay
APP
·
·
This error occurs when you're trying to map to an Email field that was previously configured but has been deleted or renamed in your Salesforce Update Record action. To fix this: 1. Open your Salesforce Update Record action 2. Check the "Object Fields" section 3. Remove the deleted Email field mapping 4. Re-add the correct Email field from your Salesforce object 5. Ensure field types match between Clay and Salesforce If you're still having issues, please share the complete JSON error message so I can provide more specific troubleshooting.
Sources: Update Record with Salesforce Salesforce integration overview | Documentation | Clay University Salesforce integration overview | Documentation | Clay University
Lean Bandioque
·
·
https://app.clay.com/workspaces/530147/workbooks/wb_0syo2ri5Rc7AeHuvcND/tables/t_0syprx2FVhF27au5gmN/views/gv_0syprx2mTRbKpy3z7Dx
Mark (Clay)
·
·
Lean, thanks for sharing this. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
1
Mark (Clay)
·
·
Looks like we've repaired this issue, and you should not see this if you create a new column that uses the waterfall as an input. Could you have a look, and let me know if you still hit a roadblock?
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.