Browse docs

Page List Commands

Rules, limits, and edge cases for page list commands.

Source scopes

Source scope What to know
All pages Pulls from any currently shared page and stays limited to basic page fields
Database items Supports richer filters and database-property quick actions
Selected pages Good for curated or documentation-focused lists

Layout and behavior rules

  • Setups with both Notion and a Discord server install start with /pages, a normal All pages list sorted by last edited time with Details in each row and Add comment plus Upload files on the details card.
  • Row fields decide what people see in the list itself.
  • Each Discord card shows up to 10 rows. If more than 10 pages match, the card shows the exact total and people can click Show More for the next set.
  • Page details decides what they see after clicking Details.
  • Quick actions belong on the details card, not in every row, so they only apply when the list includes Details.
  • Use a header row only when people need a short hint before scanning the list.
  • All-pages and selected-pages lists stay limited to basic page fields and filters.
  • Database lists support the richer filter model, including fixed dates and rolling date values like Today, Tomorrow, Days from now, and Days ago, plus Status, Select, and People quick actions. All list sources can use Add comment and Upload files buttons on details cards.
  • If a list uses is me, the runner must be linked through Account Linking.
  • Files uploaded into Notion can appear as Discord attachments on page-details cards. External file blocks stay links.
  • The saved Card language localizes both the list and the page-details card.

Draft setup

  • New page lists can be saved as drafts from the editor and reopened from Discord Commands with Finish setup.
  • Drafts do not register slash commands, answer Discord requests, or appear in the public API.
  • Draft command names do not reserve slash commands until the page list is created.
  • While the editor is open, switching sources or databases keeps unsaved source-specific setup for each source so you can switch back before creating or saving.
  • Drafts count toward the page list limit until you create or delete them.
  • Existing saved page lists use Save changes; NotiCord does not create draft branches for existing lists.

Naming and preview rules

  • Page-list slugs must be unique inside the connected Discord server install.
  • Preview uses the current draft rather than the last saved version.
  • The in-app preview is read-only.
  • Page-list previews keep Details buttons disabled until the list is saved.
  • If the saved source later breaks, the page list stays visible with a configuration error instead of disappearing.
Support