Trouble Creating New Salesforce Account Due to Missing Fields

Andreas W.

Hey team, Running into something writing to Salesforce, creating a new account.

[{"message":"Required fields are missing: [Name]","errorCode":"REQUIRED_FIELD_MISSING","fields":["Name"]}]

But I populate Account Name which is the correct field (looking at SF Object Manager)

12 comments

Channeled
APP
·
·
The error you're encountering suggests a mismatch between the field names in your Clay setup and Salesforce requirements. In Salesforce, the "Name" field is typically used for Account names. To resolve this: 1. Double-check your field mapping in Clay to ensure "Account Name" is correctly mapped to "Name" in Salesforce. 2. Verify that the "Name" field is populated and not left blank. 3. Ensure the field types match between Clay and Salesforce. If the issue persists, could you please copy and paste the full JSON response into the chat? This will help us troubleshoot further.
Sources: Create Record with Salesforce Salesforce integration overview | Documentation | Clay University
Andreas W.
·
·
https://app.clay.com/workspaces/413658/workbooks/wb_6sCr7RDgjxwj/tables/t_7j5QvzwVfhnZ/views/gv_B6riHWzBzpdj
Andreas W.
·
·
pls help
Daniela D.
·
·
Hey Andreas! Apologies for the delay. The cell returned that error because the input provided does not yet exist for that row. For context, the "company field" is being extracted from "enrich person", but only one cell in that column has run. Once the cell runs, the company name will populate and the SF action will run correctly. Let me know if that helps!
(24 kB)
1
Andreas W.
·
·
Thanks Daniela. fyi, I spoke with Bruno R. about this as well. It’s difficult to integrate this into a CRM since we need to wait for data for the events.
Daniela D.
·
·
Hey Andreas! Happy to help✨. To confirm the issue: You're not able to consistently auto-update/create records in SF due to enrichments (that provide inputs) not auto-running or due to the event trigger?
Andreas W.
·
·
Hey Daniela, thx. Not qyite. It’s super hard for me to build CRM integrations when I just created the Job Change Tracker thingy since the CRM integrations need the data in the table so I can reference and map them.
Mark L.
·
·
Thanks, Andreas. So this seems more of a feature gap than defect per se. As in, it's difficult to complete setup for later/dependent columns... when we need understand the shape of the incoming data in order to complete the settings. I can share this with our internal product/engineering teams. Would love this to be more seamless, especially in many cases when Clay itself knows the format of the anticipated data, like Enrich Person. Appreciate you raising this!
1
Andreas W.
·
·
Thx Mark, exactly. Good to know you’re raising this, it’s in the way of smooth implementation. Keep me posted pls!
Mark L.
·
·
I know the team has done some work lately mapping all the inputs/outputs from the various integrations, in anticipation of "table-level AI", so to speak. I think this sort of idea would dovetail very nicely. I'll be following along the internal thread I raised, so if I get any juicy morsels on future plans, I can pass them along. :) For now, I'll tentatively mark this closed for the moment, since I don't think we have any other items to tackle here. But please keep in touch if you hit other roadblocks!
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.
Andreas W.
·
·
hey hey - did you change something already Mark L.? IDK but this is perfect - I see a bunch of folks in there and can wire it up as I need