Set up a Notion cookbook template for your recipes

Start with the Cookbook template

Connect Notion from Recipe Clipper and complete the Cookbook template setup in your own workspace. You can edit the resulting database in Notion. Before saving a recipe, open Recipe Clipper Settings and confirm that your cookbook is the database marked In Use.

If you use an existing recipe database, share it with the connection and check the property names and types below. The app uses the first accessible database returned by Notion. Settings shows the database in use; it does not provide a database picker. Re-authenticate to change which pages and databases the connection can access.

To get started: Connect your Notion workspace

For workspace permissions: Notion's guide to managing connections

Keep these recipe database properties

The title property can have any name. The other imported properties must keep these exact names and types. Recipe Clipper matches those fields during each save and skips a field if its name or type no longer matches.

The full ingredient list and cooking steps live in the page body. The Ingredients database property holds ingredient names without amounts so you can filter for a food you have on hand.

For adding or changing properties: Notion's database property reference

Make views for the way you choose dinner

Start with a table view while checking imports. It makes missing times and property values easy to spot. Once the data looks right, add views of the same database instead of copying recipes into separate databases.

• Quick dinners: filter Cook Time (mins) to 30 or less, then add Tags contains dinner if that tag appears in your collection. Cook time does not include preparation time, so check both values when time is tight.
• Use what you have: filter Ingredients to contain a specific ingredient, such as chickpeas. Use the actual ingredient names in your cookbook; imported names may need tidying for consistent filters.
• Easy recipes: filter Difficulty to Easy. Review the label yourself after cooking, because the importer may infer it.
• Browse by photo: add a gallery view and use page covers as card previews. A recipe without an extracted image may need a cover you add yourself.

For the Notion controls: Notion's instructions for views, filters and sorts

Add your own notes and meal planning fields

Add properties for things the importer does not know: a Tried checkbox, your own Rating, or a Last cooked date. These are your fields to maintain. Recipe Clipper fills its supported recipe properties when creating a page and does not fill your custom fields.

If you already have a meal planner database, add a relation to your cookbook so a planned meal can point to its recipe page. That relationship is something you set up in Notion; Recipe Clipper does not automatically schedule meals or build a shopping list.

Keep substitutions and cooking notes in the recipe page. Leave the source URL intact so you can compare changes with the original. You can hide imported properties in a view when you want a quieter layout instead of deleting or renaming them.

Check one import before adding more recipes

1. Save one recipe with ingredients and written instructions.
2. Confirm that it appears in the intended cookbook, with its ingredient list and steps in the page body.
3. Compare the imported properties with the original recipe. Fix amounts or times that need attention.
4. Try an ingredient filter and a cooking-time sort, then open the recipe on the device you use in the kitchen.

Ready to add the first page: Follow the recipe import walkthrough