Notification Rules

Use this page when you need the exact behavior of a notification rule. Real-time and scheduled-change rules can watch all shared pages, one database, or one page, with source-specific limits described below. If you are setting up your first rule, start with Get Notifications in Discord.

New notification rules start with the default name Notification rule until you rename them.

Every rule has four parts

1. Source: all shared pages, one Notion database, or one Notion page
2. Target: the Discord destination to send notifications to
3. Delivery timing: real time or scheduled changes
4. Trigger: the event types that should create a notification

Targets

Every rule sends to exactly one Discord destination:

• Discord channel: a shared channel the NotiCord bot can post in
• Direct message: one fixed linked account chosen from Linked Accounts

Direct-message rules do not dynamically follow assignees, mentions, or the person who triggered the change. You choose the DM recipient explicitly; NotiCord does not auto-pick one. If that linked account is later unlinked or Discord cannot deliver DMs to that person, the rule will block or pause until you choose a working destination and save again.

Channel rules can also add fixed Additional mentions in Notification content:

• choose fixed Discord users or roles to mention whenever that rule sends
• these mentions stay fixed for the rule; they do not automatically follow the current assignee
• previews still render the mention line, but Send preview suppresses the actual ping

Sources

All pages

Watch any currently shared page in your connected NotiCord workspace.

All-shared-pages rules:

• can use real-time or scheduled-change delivery
• can watch new pages, page/item updates, and comments across shared pages
• use the same notification wording options as real-time database rules
• do not support database-specific watched properties, advanced filters, or quick actions until you switch to a specific database
• scheduled all-pages rules use page-generic row fields and changed item details fields only

Database rules

Watch items inside any shared Notion database.

Database rules can use:

• real-time or scheduled-change delivery
• changed-property triggers and current-item filters on real-time rules
• watched properties and current-item filters on scheduled-change rules
• quick actions on real-time rules that send to a Discord channel
• quick actions on changed item details cards for scheduled-change rules in shared channels and direct messages

If a previously working page or database is later archived, deleted, or no longer shared with NotiCord, the rule stays visible with a blocked source warning so you can restore access or switch to another source.

Page rules

Watch one standalone page that is not part of a database.

If the page is missing in the picker, open Can't find your page? to refresh the list or paste the page URL/ID directly.

Choose one page scope:

• Selected page only: only that page
• Child pages only: only nested pages beneath that page
• Selected page and child pages: both

New page rules start with the selected page and child pages.

For page rules, New subpages means a new subpage under the selected page, so the page scope must include child pages for that event to do anything.

Page rules can use:

• real-time or scheduled-change delivery
• the same selected-page versus child-page scope in both delivery modes
• page-generic scheduled row fields and changed item details fields only
• no database-specific watched properties, advanced filters, or quick actions

Delivery timing

Real time

• Available on all-shared-pages, database, and page rules
• Sends notifications when Notion sends a matching new item, update, or comment event
• Usually arrives within 1 to 5 minutes

Scheduled changes

• Available on all-shared-pages, database, and page rules
• Checks the selected source on a schedule and sends notifications only for new or updated pages or items since the previous run
• Groups matching changes into one notification per run
• Sends one interactive notification list for the matching items from that run
• Each matching item can open its own changed item details card
• Supports New items, Item updates, or both
• Database scheduled rules can narrow Item updates to selected watched properties, or leave that picker empty to match any supported property change
• Supported scheduled watched-property types on database rules are Title, Text, Number, Date, Checkbox, Email, URL, Phone number, Status, Select, Multi-select, People, Relation, and Formula
• All-pages and page scheduled rules use page-generic row fields and changed item details fields only
• Notification content and changed item details are configured separately
• Database scheduled changed item details cards can include quick actions in both shared channels and direct messages
• Daily runs use the selected timezone and run hour
• Hourly scheduled changes are available on Team only
• Moving a daily run later to an hour that has not happened yet can make it run again that same day. Moving it earlier waits until the next day.
• Comments are not supported on scheduled changes
• Files and Rollup do not count for scheduled watched-property matching on database rules

Trigger types

New items

• Real-time database rule: a new item was created in the database
• Scheduled all-pages rule: a new shared page was created since the previous scheduled check
• Scheduled database rule: a new item was created in the database since the previous scheduled check
• Scheduled page rule: a new subpage was created inside the selected page scope since the previous scheduled check
• Page rule: a new subpage was created under the selected page

Item updates

Real-time rules that watch item updates can use:

• Property changes on database rules
• Content edits on database rules
• Title changes on page rules
• Content edits on page rules

Scheduled changes can watch:

• New items and Item updates since the previous run on all supported source types
• selected watched properties for database item updates, or any supported property change when the picker is left empty

Comments

• Fires when a new comment is posted on the selected source
• For page rules, comments follow the same selected-page versus child-page scope as updates
• Comment notifications can include comment text
• Comment attachments are not included
• Comments are real-time only

Real-time changed properties and advanced filters

These controls apply only to Item updates database rules with Property changes enabled inside the Notify when group.

Only when these properties change

• No properties selected: any supported property change can trigger the rule
• Selected properties: only those changed properties can trigger the rule
• Supported trigger properties: Title, Text, Number, Date, Checkbox, Email, URL, Phone number, Status, Select, Multi-select, People, Files, and Relation
• Formula stays visible in the picker with a Scheduled only badge and a note that scheduled notifications support that field
• Rollup stays visible in the picker with a Not supported badge instead of disappearing from the list

Advanced filters

• Advanced filters live in their own separate section on the rule page
• Each filter row checks whether the item matches that filter right now
• Filter rows are combined with AND
• The section starts collapsed until the rule has at least one saved filter row
• Supported operators depend on property type
  • text-like properties and string formulas: Contains, Is, Is not, Is set, Is not set
  • Status, Select, Multi-select, Checkbox, and boolean formulas: Is, Is not, Is set, Is not set
  • People: Contains, Is, Is not, Is set, Is not set
  • Number and number formulas: =, !=, >, >=, <, <=, Is set, Is not set
  • Date and date formulas: On, Before, After, On or before, On or after, Is set, Is not set
  • Relation: Is, Is not, Is set, Is not set
• People filters can either choose specific Notion users from the connected workspace or use Contains to match the visible Notion name text
• People contains is best for external collaborators whose Notion guest account is not in the workspace-wide picker
• Relation filters let you search the linked related database and choose one related page
• Formula filters need at least one database item so NotiCord can detect the formula value type
• Files and Rollup stay visible in the picker with a Not supported badge
• If a saved Status, Select, Multi-select, or People filter value disappears from Notion later, the editor keeps that unavailable value visible in the picker and blocks preview and saving until you replace it or remove the filter

Current-item filters can use these property types:

• Title
• Text
• Number
• Date
• Checkbox
• Email
• URL
• Phone number
• Status
• Select
• Multi-select
• People
• Relation
• Formula

Changed-property triggers and advanced filters are separate. For example, you can trigger only when Status changes, then require the current Assignee to match a specific person before sending a notification.

Notification rule quick actions

Database rules can add up to 5 quick action rows.

Real-time rules:

• Quick actions are available only when the rule sends to a shared Discord channel
• The quick actions render directly on the notification card

Scheduled-change database rules:

• Quick actions render on the changed item details card, not on the notification list itself

• Scheduled-change quick actions work in both shared channels and direct messages

• Each row is either a button row or a dropdown

• Button rows support up to 5 actions

• Button rows can mix actions from different supported properties

• Dropdowns support up to 25 options

• Supported property types: Status, Select, and People

• Dropdowns support Status and Select only, with one property per dropdown

• After you pick a compatible database, the first button row is added automatically when supported quick actions are available

• Button-row pickers show a short property status such as 2 available from Priority or All Priority buttons selected

• When a button row is full, the builder points you to Add button row or removing a button in that row

• Top add controls disable themselves when that row type has no unused actions left or the quick-action row limit is reached

• Configured buttons and dropdown options stay visible even when the item already has that status or select value

• Notification rule quick actions are configured separately from create-command quick actions

See Quick Actions for setup details.

Notification content

Real-time rules expose the full notification builder described below.

Scheduled changes use a two-step notification shape:

• a notification list with the selected row fields, including Title when you choose it, and optional row mentions from visible People fields
• a changed item details card with its own selected detail fields, plus optional quick actions on database scheduled rules

Required field selections:

• Scheduled-change notification lists need at least one selected row field before saving or previewing the list
• Changed item details cards need at least one selected details field when the list includes Details
• Real-time item or page notifications need at least one selected displayed field when Selected properties is enabled
• Comment notifications need at least one selected displayed field when comment field selection is enabled
• Channel rules can add fixed Additional mentions inside Notification content

Real-time notifications can include:

• notification line, including the actor name when Notion provides one
• linked title
• plain title
• page or item content
• selected properties
• quick actions

Changed item details cards for scheduled-change rules can include:

• notification line
• linked title
• plain title
• page or item content
• selected detail fields
• quick actions on database scheduled rules only

Comment notifications can include:

• comment line, including the commenter name when Notion provides one
• linked title
• plain title
• comment text
• page or item content

When a rule includes page or item content, the Discord card adapts that content to Discord's component layout instead of trying to recreate the full Notion page.

• Text keeps its reading order, even when images or video blocks appear between paragraphs
• In Notification content, you can choose whether images and direct video files render inline where they appear on the page
• You can also choose whether downloadable PDFs and generic files render as Discord file components at the bottom of the card
• In Notification content, the selected-properties picker includes every non-metadata database property except the title field, including Files, Formula, and Rollup
• URL properties render as clickable links in the Discord card and in the in-app preview
• Relation properties render related page titles as clickable links when NotiCord can resolve those related pages
• Use the dedicated title fields when you want the page or item title in the card
• Selected properties stay visible even when they are empty, using a clear placeholder instead of disappearing
• Show empty fields is on by default in Notification content. Turn it off if you prefer tighter cards.
• Multi-column layouts are flattened in reading order
• Tables are summarized into short row lines
• Linked pages and databases render as labeled summary lines
• Bookmarks, embeds, and web-style link previews stay as labeled links when they are not direct media assets
• Long content is trimmed to fit Discord card limits

Each rule can choose the word used in the notification line when that line is included. This changes phrases such as Alex updated this task and Alex commented on this task. Scheduled-change rules use the same saved singular label on the notification list and changed item details cards.

• Database rules: Page, Item, Task, or Custom...
• Page rules: Page or Custom...
• All pages rules: Page, Item, Task, or Custom...
• Custom... uses one singular name such as issue, release note, 問題, or 🚀 release
• Custom labels can use any short single-line text, including non-English words and emoji
• Discord mentions such as @everyone and <@123> are not allowed in custom labels

All pages rules default to Page wording. Database-item rules default to Item wording. Use Page or Task explicitly when that reads better for your rule.

This changes notification wording only. It does not change quick actions, slash commands, or other task-database behavior.

Each rule also has a Card language setting.

• Supported languages: English (US), Português (Brasil), Español, Polski, Français, 日本語, Deutsch, 한국어, 繁體中文, Italiano, Bahasa Indonesia, Türkçe, and Nederlands
• This localizes real-time notification cards plus scheduled-change notification lists and changed item details cards, including Send preview and the in-app preview
• This does not localize the rest of the dashboard UI
• Notion-authored content, property names, status/select option names, and your custom singular label are not translated

If part of the page body cannot be read in Notion, the notification still sends and history shows Sent with warning.

Rule history reuses the rule's configured singular label when available, but history itself stays in English even when the Discord card language is something else.

The preview on the rule page mirrors the live Discord wording, card language, visible fields, content media/file choices, and quick-action visibility for the selected rule.

Real-time rules default to one real in-scope page or item from the selected source when possible. You can switch the sample from the preview dropdown, but only to other in-scope pages or items for that rule.

If NotiCord cannot find a usable real sample yet, the real-time preview falls back to example content. For Item updates, Page updates, and Comment previews, the event line can be simulated even when the page or item content is real.

When preview content is synthetic, the fallback people and actor identity come from the subscription owner instead of a generic sample user.

Scheduled changes use a live rows preview instead. That rows preview reflects the current draft and shows the items that currently match the scheduled-change setup. It does not prove the exact next scheduled delta, because real scheduled runs still send only changes since the last run.

Send preview sends the current draft preview to the selected destination, so you can check delivery before saving.

• The in-app preview is read-only, so buttons and links work only in Discord
• Preview suppresses pings, even when it shows the same mention label Discord will show live
• Sent real-time preview notifications use the same live quick actions, footer, and media/file rendering as the current draft card
• Scheduled-change preview notifications still keep list Details buttons disabled
• If preview is blocked because a required displayed-field selection is empty, the preview rail explains the missing selection instead of rendering a generic invalid card
• The current card stays visible with a loading indicator while the preview refreshes after a sample or config change
• Structured page body content such as toggle text, callouts, numbered items, and small tables stays in the card when it fits. Small tables render as aligned Discord tables with up to 5 rows and up to 3 source columns plus an ... overflow column when more columns exist
• Preview notifications do not create Notification History rows
• Preview confirms Discord delivery for the current draft only; it does not confirm that a future Notion change will match the rule
• Direct-message previews need one linked account and can fail if Discord does not allow DMs to that person

Discord mentions

Each rule has a Ping people in Discord toggle.

• Linked users can render as Discord @mentions in people properties and content
• Channel rules can add fixed Additional mentions for selected Discord users or roles
• If pings are off, names can still render without actually pinging
• Rule previews can show the same Discord-style mention label the live card will show without pinging anyone
• The person who triggered the change is never pinged

Users must be personally linked first. See Account Linking.

Rule health and fan-out

The rules list shows each rule as Healthy, Waiting, Paused, Blocked, Recent failure, or Off.

• Healthy means the rule has sent a real notification successfully.
• Waiting means the rule is on but has not sent a notification yet. The detail line tells you which Notion change the rule is waiting for. For real-time rules, that change should produce the first Discord notification. For scheduled-change rules, that change needs to happen before the next scheduled run. Scheduled-change rules can also show whether they are still waiting for the first scheduled check or are waiting for the first sent result after the last run.
• Paused means NotiCord stopped the rule after a deterministic Discord delivery failure, such as a deleted target channel, lost bot access/permissions, an unlinked DM account, or a user whose DMs are unavailable. Fix the destination issue, then turn the rule back on with the list toggle.
• Blocked means the rule has a configuration or availability issue that needs attention, such as an unavailable Notion source, a missing Discord permission on a channel rule, or a DM target that is no longer linked.
• Off means you turned the rule off yourself.

When a rule first enters Paused, NotiCord sends one warning email if warning emails are enabled in Settings → Email Preferences. You can open the same page from Account Settings or from the footer links in NotiCord emails.

If the Notion source is later deleted or unshared, the rule shows Blocked and will not run until you pick a working source and save again.

If multiple rules match the same event, NotiCord sends one notification per matching rule. Each Discord notification counts separately toward usage.

See Notifications Not Working if a rule is not sending notifications.