About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Zap transfer "object of type 'NoneType' has no len()" error - Airtable > Keap

  • 22 June 2023
  • 1 reply
  • 67 views
Kate Hills

Hi, I run into an error setting up a Zapier Transfer with Airtable as a source and keap as a target (add tags when new record is created in Airtable view). 

 

I’m getting the error message “

There was a problem fetching your Transfer

Error during execution: object of type 'NoneType' has no len()”

icon

Best answer by SamB 22 June 2023, 16: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.

1 reply

SamB
Rank
Userlevel 7
Badge +11

Welcome to the Community, @Kate Hills! 🙂

Ah, it looks like this error has come up before in the Community: 

There’s a bug report that’s mentioned on that topic so I’ve gone ahead and added you to the list of users being affected by it. I can’t make any promises as to when it will be resolved by but we’ll definitely send you an email notification the moment it gets fixed.

Since this is already being discussed in another topic I’m going to close out this post so that we can keep track of all interested folks in one place. For anyone who comes across this and wants to be added to the list of affected users, please reach out on the main topic for this bug directly. I’d also recommend subscribing to that topic to be kept informed of any news or workarounds shared there!

Terms & Conditions