A number of people have been running into issues with unhelpful errors from zapier so I wanted to provide an update on some changes we made that hopefully should make them more useful.
When our API gets a request to create a CMS item where the provided data doesn’t match the schema of the Collection, we return a ValidationError. For most API consumers, the returned value is useful and looks like this:
{
"msg": "Validation Failure",
"code": 400,
"name": "ValidationError",
"path": "/collections/58815a5371f812939a0d6b08/items",
"err": "ValidationError: Validation Failure",
"problems": [
"Field '_draft': Field is required",
"Field 'option': Value is not a valid Option: 123"
]
}
where it shows exactly which fields are failing validation.
However unfortunately, Zapier does not display the full error message, they show what they believe to be the “important” bit of it - which in our case, is not all that useful.
I just updated our error handling code specifically for Zapier to try and “trick” it into displaying a more useful message. It still is not perfect as it still is truncating the message, but hopefully now the error should at least be a little bit more useful.
If you’re still seeing cryptic messages, let me know and I’ll see what I can do to fix them. I’ve also reached out to Zapier’s support team to see if there is anyway we actually can control the exact message displayed.
