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 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.

Question

Line items of type 'file' - error: ‘Object of type LazyFile is not JSON serializable’

  • 21 December 2021
  • 1 reply
  • 292 views
S
Userlevel 1

Hi, I am trying to use a line item field of type ‘file’. Unfortunately this lead me to an error: ‘Object of type LazyFile is not JSON serializable’.

Context: I am developing an integration with CLI and this happend while designing an action. The example input data for the action is a mail attachment from the G-Mail integration. If I use OneDrive as a trigger (file uploaded) the error does not occure. Maybe this has something to do with hydration.

I also tried extracting the file field out of the line items. This worked for me and does not lead to any error. I am not sure whether this is a bug or I did something wrong.

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

R
Userlevel 1

I encounter the same issue..
Did you find a fix for that ?

 

Thanks

Terms & Conditions