Skip to main content

The Notion “Find Database Item” action has the option to “Create Notion Database Item if it doesn’t exist yet”. When this check is enabled, I can create a database item in notion and fill out several of the item’s properties in the step. However, many of the properties are missing. In my case, the notion database has 19 properties, but Zapier only lets me set 13 of them. This is when filling out the properties of the item to be inserted into the database, not when searching for items.

 

Instead of using the “Find Database Item” action, I can use the “Create Database Item” action. This action lets me configure all 19 properties in Zapier. However, I would prefer to use “Find Database Item” because this prevents me from adding duplicate items to my notion database.

Hi ​@dsem 

Help links for using Notion in Zaps: https://zapier.com/apps/notion/integrations#help

 

I can't see all fields in my Zap

Not all Notion property types are supported in Zapier. The following property types are not supported:
  • Files and media
  • Formulas
  • Relations
  • Rollups
  • Status
These property types will not appear in your triggers or actions.

Hey ​@dsem, just checking in 👋 Did Troy’s reply help you to get things sorted? 

Let us know whether you still need any help! 🙂


Hey ​@dsem - I think the way this action works is that, when creating a new item if an existing one is not found, it automatically populates all the properties that you are searching by with whatever values you entered in the search query. This is consistent with the way filtered linked database views work natively in Notion - when you add a new database item from a view, the new record is created with the filtered properties automatically populated to match the filter conditions.

Is your initial search step looking at 6 of the 19 properties?


That makes sense. No my initial search is only looking at 1 of the properties. It looks like this is working as designed but the design doesn’t fit my use case. Thanks for responding.


@dsem in that case, you can just add a second Create Database step after the Find Item step, with a filter or Path in between so that that only happens if the Find step comes up empty.