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.

Getting “Censored” back in api responses from ShareFile, needing a solution. This appears to be related to this topic 

 

Hi there @Casey Kleinman,

Welcome to the Community! 🎉

I did some digging into this, and it looks like the bug is still open. However, I have added you as another affected member of the bug. Rest assured that we will keep you updated via email as soon as the bug has been fixed.

I appreciate your patience and understanding.

This bug is not fixed yet, 4 months after the first reports on this community (

)

 

It’s also affecting Notion integration. The pagination cursor is being censored: 
 

Response Data Next Cursor

next_cursor

:censored:36:2db3de107a:

Hi @airton18392839821. Thanks for reaching out to let us know that you’re experiencing this issue with the Notion app as well. 

It looks as though the original Community topic tracking users being affected by this issue was automatically closed. I’ve re-opened it so we can continue to reference that as the main topic to share any updates in. I’m closing to close this topic out now. 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. 

Thanks for everyone’s continued patience in the meantime, it’s much appreciated! 🙂

Terms & Conditions