This zap has been working for a year with no problems. It is supposed to match a text string from an incoming email to a page in my notion database. The email match is triggering the zap, but then it is failing when it comes to the “Find Database Items” action.
The database I’m looking for in my notion account is available for me to select from the dropdown menu so it’s obviously connected correctly. I’ve selected it in the screenshot below. However there are supposed to be additional fields there that I should be able to use to filter which specific item/page i want from that database but they’re gone. The fields I was previous filtering in this action are now considered "Extra Fields" which are ignored in the action and are grayed-out below. How can I get them back? Why did this just start happening today?
Page 1 / 1
Hi @VatcheM
Try updating the Zap step and the connected Notion app account used in the Zap step to the current version Notion Zap app integration version which is 2.20.0.
I’ve connected it to the 2.20.0 version and it’s still doing the same thing. It is also affecting my “Update Database Item” actions. All started suddenly today. I’m assuming notion, or more likely zapier, made an update yesterday that broke the integration.
In this screenshot the arrow is pointing to where all the notion properties that you’d want to update are supposed to be and below the ones that were previously working can be seen as “Extra Fields” that are now ignored.
I’ve already opened a ticket, but in my experience I won’t hear back for a while unless I upgrade my subscription to a higher pay tier. Thanks for your replies
We’re experiencing the same issue, zap has been working fine since May broke this afternoon.
Hi @VatcheM, this is actually a bug with the latest version of the Notion integration (don’t update if you haven’t already). Notion made a breaking change in version `2025-09-03` in their API, which allows for databases to have multiple data sources nested inside them.
If you’ve tried this feature, you’ll notice that the latest version of the Zapier Notion integration no longer works for those databases, because the API now requires you you specify a `data_source_id` when making an API request. Previous versions of the API simply required a `database_id`, but that’s no longer sufficient now that a single database can have multiple data sources nested inside it.
You can find more details in my comment on this post, along with a temporary workaround via a Custom Action:
Hi @VatcheM ,
Ali here from Zapier support. It seems you might be coming across a recently reported bug with the Notion app.
I would recommend reaching out to our support team so they can specifically review your Zap and once they can confirm it is a bug, they can add you to our bug tracker so you can be notified as soon a fix is launched.
Thank you,
Hi @VatcheM ,
Ali here from Zapier support. It seems you might be coming across a recently reported bug with the Notion app.
I would recommend reaching out to our support team so they can specifically review your Zap and once they can confirm it is a bug, they can add you to our bug tracker so you can be notified as soon a fix is launched.
Thank you,
Hi Ali, yes I already have a ticket with the support team. I currently can’t use zapier for anything because of this issue since Notion is the central application of my business. I’m panicking pretty bad right now and am praying for a fix in the next few days.
Hi @VatcheM, try rolling back your affected Zaps to an earlier version that used an older version of the Notion integration. That should work, as long as your databases only have a single data source within them.
This requires a bit of familiarity with REST APIs, so if you need any help, feel free to PM me.
Reselect the notion database, it might get the fields back
Hi all - if you’re on the bug report list, you should have gotten an email recently stating that it’s been fixed, but I don’t think it has been. Here’s a detailed write-up of what I think is still going on:
Hi all,
I think this is finally resolved. You may need to edit your affected Zaps to re-select the appropriate data source (which has a different ID from the database), but once you’ve done that and re-published, it should work!
@DennisWF my database still has one data source and no changes were made. However, I still experience the same with the data source’s properties not showing. It happens only on one data source though. My other databases that turned into a data source seem to be working just fine. I already tried disconnecting and reconnecting Zap to that database but it didn’t resolve the issue. When I map it out with create a data source item and select that data source, it shows the correct data source ID but the properties still won’t show on the configuration part.
@Tom_D I think that with the fix the Zapier team implement, we’ll need to update all our Zaps that involve Notion database/data source steps, because now those Zaps are targeting the data_source_id, rather than the database_id, and even for single-source databases, those are two separate IDs. So basically, we need to go through all our Notion steps and re-select the right data source, which will have the same name as the parent database if there’s only a single data source, but with a different ID.
Looks like a recent change caused the filtering fields to move to “Extra Fields” and become inactive. Try reconnecting your Notion account or checking for app updates to fix this issue.
