Hello Clay S. I have a problem with this table (see thread), where the LaGrowthMachine insert/update is falling. Do you log API calls with error message somewhere?
For Write to Table integration errors, you may encounter specific error messages that indicate what went wrong. Common issues include: 1. "Invalid credentials" error - This occurs when your API key is incorrect or missing 2. "You cannot write to the selected table" error - This happens with invalid or conflicting data, such as: • Writing to a deleted column • Sending data to a table that references another tableTo resolve these issues, you can: ** Check and reconfigure your Write to Table integrations ** Verify all columns and tables exist and are properly set up * Double-check your API key configuration Source: Write to table integration overview | Documentation | Clay University
Hi Alexandre M.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
I am not getting either of both cases… I am getting “❌ Lead not created” / “Error running integration: Error” Can you please have a look?
One common reason for the "❌ Lead not created" error could be related to data type issues. LaGrowth Machine only accepts strings as custom attributes - not numbers, booleans, or any other data types.For successful lead creation, make sure you have: 1. A valid LinkedIn URL (not a Sales Navigator URL) 2. Selected an audience for the lead 3. Converted any numerical or boolean values to strings before sending them as custom attributesIf you continue experiencing issues after checking these points, you may want to ask for human support to investigate the specific error in your case. Sources: Create or update lead with La Growth Machine New at Clay | Clay.com Automate LinkedIn messages with La Growth Machine
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
This is unfortunately not one of the cases above.
Hey Alexandre, thanks for reaching out and sorry to hear you're running into this issue. It appears this error is coming from the custom attribute 6 where a character limit is over the 1,000 character limit. This column appears to be at 1041 characters currently so I'd recommend reducing this email content slightly and retrying. If helpful, heres the character counter I used: https://wordcounter.net/character-count Let me know how this goes and if you have any other questions. :) https://downloads.intercomcdn.com/i/o/w28k1kwz/1333367933/be23a6697e596998842c69d48afb/CleanShot+2025-01-13+at+15_25_59%402x.png?expires=1736802000&signature=c284769437eb3e1b8125b60b118856cd8e5349094e520287d77344725c9fe57b&req=dSMkFcp4mohcWvMW1HO4zadDw0%2B47%2B0HDHyx8J7Y1YZY0vs9hHBC0qPwoj0j%0A1XNr%0A https://downloads.intercomcdn.com/i/o/w28k1kwz/1333370940/d3d30e072d24eda27bdb39028ba5/CleanShot+2025-01-13+at+15_28_33%402x.png?expires=1736802000&signature=1557be86c67d40f21717e44f9426c326697410346ad67ef423f040b797dee89a&req=dSMkFcp5nYhbWfMW1HO4zaW75iKszgvvJxJDMd6T7WyI8gXO%2BwEJXUCoXRJK%0AyZvi%0A
Ok thanks for it !
How did you see that?
So I can debug next time?
Hey there Alexandre thanks for reaching out, jumping in for Owen here, this info was found by checking our backend error logs, so unfortunately it is not available to user to find. However, we are currently in the process of reworking error messages so that they are clearer for users to understand and debug.
OK cool ! Thanks
Hi Alexandre M.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Thank you so much for sharing your feedback Alexandre M.!