Build Powerful Workflows With Logseq Queries

Logseq queries can turn a messy note collection into practical “data tables” and dashboards—if links and properties are used correctly. The core lesson is that property-based filtering is powerful, but properties behave differently from links across branches, so building reliable workflows often requires converting property values into links (using square brackets) when the goal is to filter other parts of the graph.

Early in the session, the discussion zeroes in on a common failure mode: combining filters with AND. A query that requires two properties will only return blocks that have both properties on the same block. That’s because properties don’t “flow” across branches the way links do. The workaround is to make property values into links—e.g., wrapping an author value like Carol DW in square brackets—so the link tagging applies to the entire branch under a parent block. With that change, downstream queries can filter by those linked values, enabling dynamic indexes such as “all notes tagged with David Perel” to appear consistently across the graph.

Date handling is another practical constraint. Dates are treated as properties, and a created-at property exists for pages created in Logseq, but it’s not automatically added to blocks. For workflows that rely on time-based review—like using the between filter to surface todos within a date range—this distinction matters. The session also flags performance tradeoffs: turning on block timestamps can degrade query and search performance, so most workflows rely on journal pages, where blocks written on a journal page inherit that date context.

From there, the session lays out a week-long progression of five use cases that build on one another. It starts with a generic index of notes, then moves to a content consumption pipeline (saving items to consume later, templating, and viewing them in multiple passes). Wednesday shifts toward content creation—turning highlights and notes into insights and using query-driven review collections. Thursday focuses on project management, combining notes and action items, using date-based review queries to find finished work and overdue tasks. The final step ties everything into a Personal Learning System that treats learning as an input→sensemaking→output loop.

The day’s hands-on challenge (Challenge 1) focuses on building a dynamic notes index. The live walkthrough targets the David Perel page: a query macro is created using the author property, producing a table view where columns can be toggled (block titles, property fields like author and status). A key technique appears in the details: links are created from property values so that the tagging applies to the whole branch, making it possible to filter other pages (like an Audience Building page) based on those values.

The session ends with practical guidance for troubleshooting: if new links or properties don’t show up in queries, reindex Logseq so the database refreshes link references. Questions about advanced wildcard behavior are deferred to Data Log, keeping the focus on Logseq’s simpler query language for this course week.