Hello community, I’m currently integrating a Gravity Form - Monday Group.
As you know, there are many fields and different types. I often encounter errors like the ones I’m sharing in this post. Would it be possible to add the specific field that is in conflict due to the type of content to these errors?
This would greatly help future integrations and, most importantly, save time, so we don’t have to check each field and content type.
Thank you, and I hope we can find a quick solution.
Hi
Help us have more info by posting screenshots showing how the Zap step is configured in the CONFIGURE tab with the field mappings visible.
Sorry, I have already corrected it by verifying field by field between Zapier and the Monday table.
What I was referring to was the possibility that, when reporting an error, the system could specify which field is triggering the error. Right now, I only see an error message with code 200, referring to a field X among thousands that a Monday table may have.
I believe this would save us a lot of time and help Zapier be more effective in resolving errors.
This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing sensitive details.
Thanks so much for following up here to share how you fixed that error, 
Definitely agree that error message could be updated to make the cause of the error clearer. I’d recommend reaching out to our Support Team to put in a feature request for the error messaging to be improved on the monday.com app. This will flag the need for more specific and helpful error messages to the developers of the monday.com app, via our internal issue tracking tool which they have access to, so that they can work on implementing that.
Seems like you’re all set for now but please do reach back out in Community if you need help with anything else at all. In the meantime, happy Zapping! 
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.