Skip to content
Tutorials Center
My learning

Topics

Lesson 36 of 36 ยท Projects and Practice

Practice: Notion Exercises

Practice what you learned: exercises on templates, automations, permissions, API requests and systems, each with a runnable stand-in checker and a model answer.

Reading about Notion is not the same as using it. This lesson gives you exercises for the second half of the track: templates and automations, collaboration and sharing, the API, and workflow systems. Each exercise has a goal, hints and a way to check your thinking.

Notion is not available on this site. The exercises that need the app are written as tasks to do in your own workspace, with a checklist so you know when you are done. The exercises that involve logic have runnable JavaScript stand-ins where you edit code and check the result.

How to use this page

  1. Try each exercise before opening the hint or model answer.
  2. For app tasks, work in a new workspace or a test page. Do not experiment on your real team's pages.
  3. Tick the checklist honestly. If an item is missing, repeat the step.

Exercise 1: a bug report template (templates)

Goal: a database template for bug reports.

Checklist:

  • Database Bugs with Status, Severity, Reporter and Found in version.
  • A template named "Bug report" that presets Status to Triage and Severity to Medium.
  • Body headings: Steps to reproduce, Expected, Actual, Screenshots.
  • The template is the default for the main New button.

Hint: the arrow next to New opens the template menu. Remember that a view filter must not hide the new page.

Exercise 2: write the rule (automations)

Goal: describe three automations as trigger, condition and actions, then test the idea with code.

Rules to design:

  1. When a bug's Severity is set to Critical, notify the on-call person.
  2. When a task's Status becomes Done, set Done on to today.
  3. When a page is added to Requests, add a page to Tasks with a relation back.

Complete the stand-in so the rule fires only for the right edit.

JS Exercise: complete the rule

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The solution is already filled in for you to read and tweak. Try changing it so a High severity notifies a different person.

Exercise 3: who can see it? (sharing)

Goal: apply inheritance rules.

You have these pages: Company > Finance > Salaries. The team has can view on Company. Salaries is restricted to HR. Answer for each person:

  • A team member, on Finance?
  • A team member, on Salaries?
  • An HR member, on Salaries?

Check with the code.

JS Exercise: inheritance check

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Exercise 4: API request (API)

Goal: build the JSON for a query and a create request by hand, then check it.

Task: "Find tasks whose Status is In progress and Priority is High, sorted by Due ascending, 10 per page." Then: "Create a task called Write report with Priority High."

JS Exercise: check your JSON

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Exercise 5: design a system (workflows)

Goal: a small PARA-style workspace.

Checklist:

  • Databases: Projects, Tasks, Notes with relations between them.
  • A Home page with linked views: Today, Active projects, Inbox.
  • A weekly review template with a checklist.
  • A button on Home that adds an Inbox task.
  • One recurring template that creates the weekly review page on Fridays.

Self-check: can you find any task in under 10 seconds? If not, simplify.

Exercise 6: a mini project of your own

Pick one and build it using what you learned:

  • A reading list with Status, Rating and a "Finish" button.
  • A meal planner with a recipes database and a weekly calendar view.
  • A study tracker with courses, topics and a spaced-review date.
  • A content calendar for a blog with stages and an approval gate automation.

Write down: which databases, which relations, which views, which automations. If you cannot explain why each property exists, remove it.

Model answers

  • Exercise 3: the team has can view on Finance (inherited) and no access on Salaries; HR has can edit on Salaries.
  • Exercise 2: the trigger is "Property edited" on Severity with a condition of "is Critical", and the action is "Send notification". Narrowing to a value avoids noise.
  • Exercise 4: the filter is a compound and; sorts is an array; page_size is a top-level number. The create body needs a parent and a title.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. Why should you practice on a test workspace or page?

    Rules and permissions can change many pages or expose content, so practice where mistakes are cheap.
  2. 2. In Exercise 3, why can a team member not open Salaries?

    A restricted page breaks the inheritance chain.
  3. 3. A query body needs which key to limit results per request?

    page_size sets how many results come back per request, up to 100.

Summary

  • Practice with checklists in a test workspace and stand-ins for logic.
  • You exercised templates, automations as rules, permission inheritance, API JSON and system design.
  • Finish with a small project you would actually use.
  • Revisit earlier lessons in this track where an exercise felt unclear.

Next: Back to the Notion track