Notion Inline Database Filters: Property-Type Constraints and Design Boundaries

Requirements

\n

When a Notion user adds an inline filter to a database, the UI must accept the condition without breaking the page layout or losing the filter state on reload. The requirement is to understand which property types support which comparison operators, and how filter persistence is guaranteed (or not) across page views and plan tiers.

\n\n

Smallest Suitable Design

\n

The minimal working setup is a database with a single text or date property, an inline filter set to “contains” (for text) or “date range” (for date), and a shared link that preserves the filter query parameter. This design works on both free and paid plans, but persistence of the filter state after reload differs: paid plans retain the filter via a persistent link, while free plans may reset or strip the filter depending on database complexity.

\n\n

Trust and Data Boundaries

\n

Notion stores filter conditions per-page in the page's metadata. The UI-exposed conditions map to property-type-specific operators: text properties support equality “contains” and “does not contain”; date properties support range start/end; multi-select and relation properties add “contains any” and “contains all”. The trust boundary is clear: the UI reliably enforces these operators, but the Notion API returns filter objects that may include additional fields or differ in condition serialization, especially for rollup and formula properties.

\n

Plan boundaries also matter. Free–plan databases have reduced filter persistence compared to paid plans, and sharing a link from a free plan to a paid workspace does not guarantee the filter survives the cross–plan transition.

\n\n

Operational Checks

\n

To verify that a filter persists as expected, perform the following checks:

\n

\n
• Create a database, add a text or date property, apply an inline filter for a specific value or range, then reload the page. Confirm the filter is still active.
\n
• Open the page's share link and confirm the filter parameters ?filter=... are present in the URL. On paid plans, these parameters persist; on free plans they may be stripped.
\n
• Using the Notion API, retrieve the page's filter property from the properties object. Compare the API–returned conditions to what the UI displays. Note any discrepancies, especially for multi-select or relation properties where “contains any” and “contains all” may serialize differently.
\n

\n

curl -X POST https://api.notion.com/v1/pages/{page_id} -H "Authorization: Bearer <integration_token>" -H "Notion-Version: 2022-06-28"

\n

Replace <integration_token> with a valid integration token and <page_id> with the target page ID. In the API response, locate the properties section of the database–linked page and examine the filter sub–object. Expected check: the conditions array should match the UI–applied filter (e.g., [{"property": "Title", "text": {"contains": "search term"}}]). If the array is empty or contains different operators, the API and UI are out of sync for that page.

\n

Risk: API rate limits and permission scopes. The integration must have read_content scope to access page properties. Running the command outside of a properly authenticated session returns a 401 or 403 error.

\n\n

Failure Modes and Conditions That Would Change the Design

\n

Filter state is lost when: the page is moved to a different workspace without preserving the share link; the database is converted to a different property structure (e.g., changing a text property to a select); the user is on a free plan and the database exceeds Notion's implicit complexity threshold, causing the filter parameter to be dropped on reload. Nested OR groups in complex filters are limited to two branches; adding a third condition with OR logic silently collapses the group or defaults to AND behavior. If any of these conditions apply, the smallest suitable design reverts to a single–condition filter on a text or date property, or moves the filtering logic into an external tool connected via the Notion API.