Notion Must-Know! How To Use The If Statement

Notion formulas often come down to one tool: the if statement. It lets a database property return different results depending on conditions—turning raw fields like tags, text, numbers, and dates into useful outputs such as checkboxes, labels (true/false), or categorized time periods. The core payoff is practical: once the logic is mastered, most “formula confusion” in Notion becomes solvable by chaining conditions and matching data types.

The walkthrough starts by building a simple database with a formula property and a multi-select “tags” field. In Notion formulas, database properties are referenced with prop("Property Name"). For multi-select fields, the contains function checks whether a specific value exists inside the property, returning true when the second argument is found in the first. That boolean can directly drive a checkbox result, but if the goal is literal strings like "true" and "false", an if statement is used: if(condition, trueValue, falseValue). A key constraint appears immediately: the true and false branches must be the same data type. A checkbox can’t be paired with a string false without causing a type mismatch, so the transcript recommends using numbers (e.g., 1 and 0) or strings for both branches.

From there, the logic expands into “complicated” branches that perform calculations or formatting. When the true branch needs arithmetic, the formula can add number properties (e.g., number1 + number2). When the true/false branches must be numbers but source values are strings, the two number function converts inputs into numeric form. Conversely, if the output should be text, the format and format date functions ensure both branches produce strings in the same format. This matters for date comparisons: now includes a time stamp, while a date-only property does not, so equality checks fail unless both sides are formatted consistently.

The transcript then demonstrates multi-condition logic using boolean operators. A single if can combine checks such as: tags contains tag 1 AND name is not empty OR date is today. Empty detection uses the empty function, and not flips the result to mean “filled out.” Date “today” logic relies on format date with the same formatting pattern (capital L) applied to both the date property and now.

Finally, the lesson scales to multiple if statements nested together to create categories. For a date with time, the hour function extracts an hour (0–23), then chained if statements assign morning, afternoon, or evening based on thresholds (e.g., hour < 12, then hour < 17, otherwise evening). Order is crucial because earlier conditions override later ones. The same pattern is adapted for past, today, tomorrow, and future using comparisons against now and date add(now, 1 days), again with careful ordering so tomorrow doesn’t get swallowed by a broader “future” condition. Throughout, the transcript emphasizes testing with temporary “test” formulas and adding empty rows to verify each branch behaves as intended.