Real-time Notification Rules

Complete reference for configuring notification rules - the routing instructions that control when Notion updates appear in Discord channels.

Rule Anatomy

Every rule has three core components:

1. Source - Which Notion database or page to watch
2. Target - Which Discord channel to post to
3. Trigger - When to send notifications (created or updated)

Source Types

NotiCord supports two source types:

Database Sources

Watch pages inside a Notion database (including task databases). Database rules support:

• Property-based filters (select properties to narrow, or leave empty for all)
• Status filters (databases with a Status property)
• Quick action buttons (task databases only)

Page Sources (Standalone Pages)

Watch a single page that is not part of a database. Page rules can also include subpages:

• Subpages: Choose None (only this page), Direct children, or All descendants.
• Created events: Require Direct children or All descendants (the selected page already exists).

Event Types

NotiCord supports two event types: Created (new items/subpages) and Updated (changes to existing items).

• You can select one or both (default: both).
• For standalone page rules, Created means a new subpage under the selected page (requires Direct children or All descendants).

Created Events

Triggers when new items are created.

• Database rules: Fires when a new database item is created.
• Page rules: Fires when a new subpage is created under the selected page (requires Direct children or All descendants).

Updated Events

Triggers when content and/or properties change. Configuration required:

• Update Types - Choose Properties, Content, or both
• Property Filters (database rules only) - Select properties to narrow, or leave empty for all properties
• Status Filter (optional, databases with a Status property) - Filter to specific status values
• Quick Actions (optional, task databases only) - Add interactive buttons

Update Types

Choose what counts as an update for Updated rules:

• Title (page rules only) - Page title changes.
• Property changes (database rules only) - Fields like Status, Tags, or Title.
  • Select properties to narrow updates, or leave empty to watch all properties.
• Content - Changes to page body blocks and text. No property filters apply.

Property Filters (Database Rules)

When Properties is selected for a database rule, you can optionally select specific properties:

• No selection - Notify on any property change.
• Selected properties - Only notify when those properties change.

Triggers: Value changes (A→B), set (empty→value), cleared (value→empty)

Doesn't trigger: Content-only edits unless Content updates are enabled

Status Filter

Available for any database with a Status property. Requires Updated events with Properties updates enabled and the Status property selected.

Use cases: Alert on completion (filter to "Done"), flag blockers (filter to "Blocked", "At Risk"), track review stage (filter to "In Review", "Ready for QA")

Quick Action Buttons

Task databases only - Configure per notification rule:

• Status change buttons - Show buttons for all database status values
• Assign to me button - Show self-assign button (requires mapped Assignee property)

Buttons are configured separately for notification rules vs task creation confirmations. → Quick Actions Guide for setup and button behavior details

Field Selection

Choose which properties appear in Discord notifications.

Properties display as "Name: Value" with appropriate formatting for dates, people, and select fields.

Standalone page rules only offer the standard fields (no database property list).

Discord Mentions

Each rule includes a Discord mentions toggle (enabled by default) that controls whether Discord pings are sent.

• When enabled: Linked users render as Discord @mentions in page content and people properties and will be pinged.
• When disabled: Linked users still render as @mentions, but pings are suppressed.
• Excludes the author: The person who triggered the change is never pinged.

Fan-Out Behavior

Multiple rules matching the same source and event will post to multiple Discord channels. Each Discord post counts separately toward your monthly quota.

Example: Created event with rules for #product-updates and #general → posts to both channels

Alternative: Use Discord's native channel following to broadcast from one channel instead of creating multiple rules