Streaming live at 10am (PST)

Update on Zapier ValidationErrors


#1

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.


Zap Validation error
API/Zapier error! Anyone familiar with this error?
#2

Hello Nathan,

unfortunately no help for me with my latest situation... Trying to connect instagram to webflow. All worked fine first but then:

Any ideas? Collection is at zapier.webflow.io/granowall


#3

I've reached out to zapier's support about this error - I can replicate it and I too see nothing. However our API did return a normal error message. In this case, the error not being displayed should say You’ve created all the items allowed on your current plan. Add CMS Hosting to create more.


#4

Thanks @nathan! I forgot the 50 item limit. All good now with the upgraded plan.


#5

Hey, I'm getting the same error and I can't figure out why.

I'm getting data from Typeform and I checked that Reference fields are a perfect match e.g. they can choose "PR" on the form and I have a collection called "Category" which has a collection item "PR". There 3 such fields. I assumed that perfect match will work. Is this the problem?