Skip to main content
Best answer

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

  • June 22, 2023
  • 1 reply
  • 95 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()”

Best answer by SamBBest answer by SamB

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!

View original
Did this topic help you find an answer to your question?
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
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7779 replies
  • Answer
  • June 22, 2023

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!