Failed to create a http request in Dropbox argument of type 'NoneType' is not iterable error

This error usually means Zapier is getting an empty (null) Dropbox field where it expects data, open that step, make sure the Folder/File ID and tag are correctly mapped from real test data (not blank), then re-test the Zap.

 Hey ​@Miss S,

You are saying it works even after throwing the error?

You should have the understanding of API documentation to query the API directly. Here is a helpful article about it- https://help.zapier.com/hc/en-us/articles/12899607716493-Create-an-API-Request-action

Please check if /folder1 is actual path to the folder. One other thing you can try is adding a text file rather than a folder and see if it gives you the error as well. If it works then it may be a some nuances on the API side to add tags to folders. You can also try testing the API request in something like Postman and then implement in Zapier. Hope it helps! 

Hey ​@Sparsh from Automation Jinn ! Thank you for your reply.

Both files and folders are giving me this error. And it is really adding the tag to the folder/file. 

Some screenshots

Folder information in dropbox: 

The Test is giving me this:  

It is successful added, so I don’t know why its giving me this error. Even the troubleshooting is not giving me any useful information hehe. 

Hey ​@Miss S,

Bit strange that it’s working after giving the error.

Is it giving the error in live zaps and working correctly? Maybe make the Zap live and see if it’s working as expected.

Also as mentioned earlier try testing it in Postman. Hope it helps!

Even in Live, Zapier is sending me a mail with the error. Ugh I just don’t get it. 
 

I did a test in Postman, everything works there as well. 

I did read in the documentation (https://www.dropbox.com/developers/documentation/http/documentation) that the API does not return any values. So its NULL. Also seen in postman. 

Is it possible that Zapier does not handle the NULL and gives me this error? 

Hey ​@Miss S,

I think that might be it. But if it’s working then atleast then it’s doing the API call correctly. You can add Error handling if you want to add more actions after the error as Zap may stop after encountering an error.

You can reach out to Zapier support for any feedback or feature request here- https://zapier.com/l/support. Hope it helps!

Thank you so much!! 

Hi there ​@Miss S 👋

Did the error handler Sparsh suggested help to get around those errors that were due to the NULL value?

Let us know how it went, want to make sure you’re all set!