Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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.

Hi,

I am trying to set up a Zap to copy files from a specific folder in an S3 bucket over to Sharepoint.

I can connect to S3 and the bucket, but is there a way to specify the folder that it should monitor?

 

We have hundreds of thousands of docs in this bucket, so currently we receive the “Response payload size exceeded maximum allowed payload size (6291556 bytes).” error when it connects to the bucket.

 

Is there any wok around for this, or a way to specify which Folder Zap should monitor?

 

Thank you

 

 

Hi @NickBuchanan,

Welcome to the Community! 🎉

I did some digging into this, and it seems like the error you’re running into in Amazon S3 is a known bug. Our team is aware of the issue and is working on a fix. I've added your email address as another affected user. That does a few things:

  • Bring this to the attention of the integration developers
  • Help track and prioritize fixes
  • Allows us to notify you via email if/when this is fixed

Unfortunately, I do not have an ETA, but I’ve added you to the list of users affected by this issue so we can let you know as soon as we have any updates.

In the meantime, you can stay in the loop/follow along with updates on the main thread here: 

For anyone that comes across this and wants to be added please reach out on the main topic for this issue here and we’ll get you added to the bug report.

Reply


Terms & Conditions