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.

All of our Notion integrations started erroring today. I looks like the Zapier integration now only points to the unstructured part a Notion page, not finding the structured fields. This means that all of our page field fill operations return errors. Has anyone figured out a way to deal with this? 

It is probably related to a change in Notion:
 

Databases just got more powerful! Now supporting multiple data sources and linked views in a single database, creating a unified hub for your workflows.

This comes with an important API update for customers using internal integrations. Our new API version 2025-09-03 separates "databases" from "data sources,” unlocking powerful new organizational capabilities.

You are receiving this email because we detected that your workspace, CarbonDrop, has had at least one API call in the last 30 days that may be impacted by this functionality.

What you need to do:
• Update your integrations to the new API version 2025-09-03 to support multiple data sources
◦ We're introducing the concept of API versioning to integration webhooks as well
• [Recommended] Restrict permissions on mission-critical databases to prevent users from adding new data sources before API migration is complete.

Start upgrading your integrations now to ensure a smooth transition when your team is ready to add new data sources to your workflows.

 

Hi ​@paul-blackswan, ​@AnthonyOrtega and ​@Remy F thanks for letting us know. Fully appreciate how frustrating this situation is and I’m very sorry that you’re still experiencing issues with your Notion Zaps.

I know that there are other issues with larger data sources (~100+ pages) which our engineering team are still working to resolve. Please know that the issue has already been escalated and the team are doing all they can to resolve things as soon as possible. Given that you’re running into errors that are different to the ones cited for the bug mentioned earlier this thread I’d recommend contacting our Support team directly so they can help to investigate and troubleshoot things further.

Since the bug report linked to this discussion has been marked as resolved, I’m going to close this thread to further comments to keep things organized. If you’re still running into issues with your Notion Zaps, please reach out to our Support team - they’ll be able to investigate and walk through any troubleshooting steps with you directly.

Terms & ConditionsAccessibility statement