The app returned "Could not find database with ID: 25f37881-11c8-80a2-ad3a-d94e527ec6fd. Make sure the relevant pages and databases are shared with your integration.".
Co-pilot and myself have checked everything and the kitchen sink to fix it. Reconnect, rebuild, all the possible solutions.
Hi @Troy Tessalone, thanks for your reply here are the screenshots. It’s not populating any field.
The data base id that comes up is the correct one, but the error has another one. So Initially I thought it was a cache issue but after a afternoon of trying everything. I think its an api thing
@Jan Valentine
Post screenshots showing how your Zap steps are configured in the CONFIGURE tab while in EDIT mode with the field mappings visible
You need to grant Zapier access to your pages or databases. If you create new ones after connecting to your Notion account and want to interact with them in your Zaps, you'll need to grant Zapier permission in your Notion account.
I gave Zapier full access to all of my pages, but new pages don’t appear
If you create new pages after connecting to your Notion account and want to interact with them in your Zaps, you'll need to grant Zapier permission in your Notion account. This is because Notion’s API requires you to specify permissions for each page that Zapier can access.
My databases are not listed in the dropdown menu
If you're having trouble listing your database in your Zap, try these steps:
If the database you're looking for is a subpage, un-nest it, and temporarily make it a page. After the Zap finds it, you can change it back to a subpage.
After trying these steps, you should be able to refresh your fields and view your database in your Zap.
Make sure you using the current version of the Notion Zap app integration.
@Troy Tessalone You mean like this?
This was an existing zap for months.. So All the prerequisites are there.. Yes to all of the above questions. permissions, account connections.
@Jan Valentine
Make sure you have upgrade the Zap step to use the current version of the Notion Zap app integration.
Screenshot below does not show any fields configured.
Try adding data to the “Content” field, otherwise, you are trying to create an empty Item and that might be related to the error.
TIP: Click field labels to see tooltips with more info about expected field values and formats.
@Troy Tessalone I still get the same error. The database that it is seeking is not the same database ID. The zap has been working for months and broke yesterday after the notion update.
If you read it you will see that it needs a new DATA SOURCE ID tag
Below I populated the content, same error.
This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing personal or potentially sensitive details.
notion has changed there API from database ID to datasource ID. I believe this is the issue.
according to co-pilot
ROOT CAUSE IDENTIFIED: Notion released API version 2025-09-03 with breaking changes that are NOT backwards-compatible. According to Notion's developer documentation:
"Most existing database integrations must be updated to prevent disruptions" "API operations that used database_id now require a data_source_id" "Create page when using the database as the parent" and "Database read, write, or query" will fail
IMPACT: This affects ALL Zapier users with Notion database integrations. Standard troubleshooting steps (reconnecting auth, recreating steps) will not resolve this issue.
@Jan Valentine
Can you post screenshots showing how your Zap step 2 SETUP tab is configured?
Make sure you are using the current version of the Notion Zap app integration, which is 2.20.0.
In your Notion Zap step, make sure your selected Notion app account in the SETUP tab is for Notion 2.20.0.
@Troy Tessalone I change the notion as seen below.. still same error
This post has been edited by a moderator to remove personally identifiable information (PII). Please remember that this is a public forum and avoid sharing personal or potentially sensitive details.
@Jan Valentine
Try turning the Zap ON and testing live.
Check the Zap Run history details to see the DATA IN/OUT for each step to see if there is still an error.
Also, in the Zap Run history details, check the LOGS tab to see the underlying API request/response to see which Notion API version is being used along with possibly more detailed error messages to help you troubleshoot.
I saw that you choose the Notion v2.20.0 which is latest one in the last screenshot that you shared.
But after that did you configure the fields again and try clicking on the Retest step to see if it fixes it? Hope it helps!
Hi @Sparsh from Automation Jinn, thanks for your thoughts, I have and also have tried building a completely new zap after deleting all connections etc. with the 2.20 and I still get the same error.
The database I choose is not the database it want to see. As you you'll see in the screen shot the error message database begins with 25 and and below that the database I need it to see is 24.
As you'll see, in the past the connection was based on a database id but notions api changed because they now let you have multiple data sources in one database. The article is saying that all integrations based on old database id will fail as the new api link is based on a data source id. Its a completely different ID tag. SOURCE not ID.
So unless the id gets changed at the api level in zapier from database to data source all the subsequent troubleshooting is irrelevant for now.
I have upgraded to a team plan so I can get into a live chat with support but have yet to actually find where that option is.
You can close this.. I have spoken with support and they agree with my findings.
there message below
Our dev team became aware of recent updates Notion made to support "multi-source databases". These changes by Notion require updates to our integration, as it currently only supports single-source databases in Notion
This is a known bug and our devs are already on it. 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.
Our dev team became aware of recent updates Notion made to support "multi-source databases". These changes by Notion require updates to our integration, as it currently only supports single-source databases in Notion
This is a known bug and our devs are already on it. 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.
Same Problem on my and please add me to the list with users having problem. Thanks @Jan Valentine for mentioning this. I was getting crazy ;)
Hi folks 👋 I’m so sorry that you’re all running into these errors with your Notion Zaps.
@Jan Valentine - thanks so much for flagging this and for sharing the response from our Support team. Really appreciate you keeping everyone in the loop! 🤗
@Macsche, @yesman, @VatcheM and @IAMJoshuaH - I’ve made sure that everyone who wasn’t already added to the bug report by our Support team, is now on the list of impacted users. I don’t have an ETA to share, but you’ll all receive an email notification from us once it’s fixed.
Thanks for everyone’s patience while our engineers work on a fix. 🙏 I’ll follow up here with any status updates I come across. In the meantime, let me know if there’s anything else I can help with.
Running into the exact same issue. When I try to select a database in Zapier for a “find item in Notion database” step, none of the properties pop up to search by, and there’s no way to filter or add search criteria. If I run the step anyway it pulls up the same error that others in the thread have noted.
Many of my old automations have stopped working and I’m completely unable to build new ones. Would love support asap, as many of our clients are counting on these Zaps.
