Notification Rules

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

📖 New to Notifications?

This is a comprehensive reference for all notification rule options. If you're setting up notifications for the first time, start with the Get Notifications in Discord guide for step-by-step instructions.

Rule Anatomy

Every rule has three core components:

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

Event Types

Event names depend on database type:

Task databases: "Task Created" / "Task Updated"
Page databases: "Page Created" / "Page Updated"

📋 Task vs Page Databases

Task Database: Has Status property + connected on Tasks page. Supports quick actions, slash commands, custom modal fields.
Page Database: No Status property or not connected. Notifications only (read-only).
→ Task Database Configuration for complete details

Created Events

Triggers when new items are created. No additional configuration required.

Updated Events

Triggers when watched properties change. Configuration required:

Watched Properties - Select which properties trigger notifications
Status Filter (optional, task databases only) - Filter to specific status values
Quick Actions (optional, task databases only) - Add interactive buttons

⏱️ Batching Delay

Notion batches updates, causing 1-minute delays. Only watched properties trigger notifications - unwatched properties are ignored to reduce noise.

Watched Properties

Select which properties trigger notifications on Updated events. Changes to unwatched properties are ignored.

📌 Supported Properties

All Notion property types supported: Status, Assignee, Date, Select, Multi-select, Text, Number, Checkbox, People, URL, Email, Files, Formula, Relation, Rollup

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

Doesn't trigger: Changes to unwatched properties, title edits (unless title property watched), page content edits (unless content property watched)

Status Filter

Task databases only - Available for Task Updated events when Status property is in watched properties.

⚙️ Configuration

Empty: Notify on all status changes
Selected values: Only notify when status changes to selected values (e.g., "Done", "Blocked")

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.

📝 Available Fields

Standard fields:

Notification message (e.g., "New task created")
Page title (with link OR plain text)
Page content (includes @mentions when users have linked accounts)

Database properties: All properties from your database (Status, Assignee, Due Date, Priority, Category, Tags, etc.)

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

Fan-Out Behavior

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

Example: Task 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

💬 Need Help?

See Notifications Not Working troubleshooting guide

Guides

Reference