Best answer

Airtable to Webflow Zap getting “Validation Failure” error

  • 10 February 2022
  • 15 replies
  • 665 views

Userlevel 1

Hey all, 

 

I’m trying to link an airtable table to Webflow CMS via Zapier and I’ve followed all of the steps that someone previously had done and I’m still getting the “ValidationError: Validation Failure”. 

 

Here is a loom of what’s going on: https://www.loom.com/share/d0156a49e23743af94d7e6d699368867 

icon

Best answer by joshfifelski 10 February 2022, 04:57

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

15 replies

Userlevel 7
Badge +14

Hi @joshfifelski 

Troubleshooting suggestion:

GSearch on the issue returns some Webflow Forum topics to look into: https://www.google.com/search?q=webflow+validation+error+validation+failure

 

Troubleshooting suggestion:

Process of elimination.

Remove a data point one at a time to see if you can isolate the field causing the issue, OR vice versa add one field at a time to see if you can isolate the field causing the issue.

Userlevel 7
Badge +14

@joshfifelski 

Observation:

For your linked records, those would send the Airtable Record ID (see examples below).

Unsure if that’s your desired data point to send to Webflow.

If you’re looking to get the friendly name for each linked record, then you’ll need to add Lookup fields in Airtable.

 

Userlevel 1

Thanks! I hadn’t but just tried and it didn’t fix it. Everything is fresh, nothing has been renamed
 

Userlevel 7
Badge +14

@joshfifelski 

Check and try the other options I added in the comment above.

Userlevel 1

I just added those in (had no idea what that was), but even with the new fields, it’s still showing the error. 

 

Userlevel 7
Badge +14

@joshfifelski 

Might be prudent to open a ticket with Zapier Support for possible assistance while you’re at it: https://zapier.com/app/get-help

It’s a know limitation that the error responses from apps are truncated thus causing those to be misleading because they appear to be generic.

Userlevel 7
Badge +14

@joshfifelski

A more advanced possible workaround would be to use the Webflow CMS API to create the Live Collection Item: https://developers.webflow.com/#create-new-live-collection-item

App APIs can be used in Zaps with the Webhook app as an action step: https://zapier.com/apps/webhook/integrations

Testing with the Webflow CMS API will show a more complete error response.

Userlevel 7
Badge +14

@joshfifelski

Not sure if these related topics provides any guidance:

 

Userlevel 1

@Troy Tessalone - thanks for the help! I’ve been following this youtube video while doing it and it worked just fine for him, but for some reason doesn’t work for me. 

 

I’ve also just submitted a ticket to see if there’s something else going on. 

 

Super appreciate the help on this!

Userlevel 7
Badge +14

@joshfifelski 

Double check your field types in the Webflow CMS Collection.
Field types that are non-short text may be causing the issue. (e.g. dropdown, multi-reference, etc.)

Userlevel 1

@Troy Tessalone - I just started another test from scratch and really simplified the data I was sending. It worked! I was able to then isolate the problem and discovered it’s the Multi-reference fields that’s causing the problem. 

Userlevel 7
Badge +14

@joshfifelski 

Congrats!

Process of elimination for the win!

Hey @joshfifelski and @Troy Tessalone - I am encountering the problem and would love some help. 

Loom below 

 

 

Found the issue! A category on webflow had a lowercase whilst on airtable it was uppercase. Damn that could have taken a lot longer to resolve ! 

Userlevel 7
Badge +9

Thanks @joshfifelski and @Rory-trumpet for looping back around with your solutions! So glad ya’ll were both able to get this sorted. 🎉