Get Notifications in Discord

Get automatic Discord notifications when pages and tasks are created, updated, or commented in Notion.

Important: Task notifications need a task database

Want task-only features (quick actions)? First connect the database as a task database on the Tasks page. Otherwise you will still see Created/Updated events, but without task-only features. Status filters work for any database with a Status property. The rule editor shows a task features callout under the database picker when a database is not connected.

Before You Begin

📋 Prerequisites

Notion access: Share the database or page with NotiCord in Notion. If you can't find it in the picker, follow Give NotiCord Access in Notion.
✅ Already shared during setup? You're good to go!
Discord permissions: Bot needs these permissions in target channels: View Channel, Send Messages, Embed Links, and Attach Files. Without these, notifications will fail to post.

📄 Standalone Pages

To watch a page that is not in a database, share the page with NotiCord. To watch subpages, share the parent page so subpages inherit access. If it doesn't appear, follow the Notion access guide.

Step-by-Step: Create Your First Rule

Go to the Notifications page
Click "+ New Rule" (or Create First Rule on the empty state)
What to Monitor: Choose Database items or Page
Select the source:
- Database items: Pick the database from the list
- Page: Open the page picker and search or choose a recent page
(Page rules) Choose Include subpages? → No subpages, Direct children, or All descendants (Created requires Direct children or All descendants)
Where to Send: Select a Discord channel
When to Notify (multi-select):
- Created - Notify when new items are created (or new subpages for page rules)
- Updated - Notify when existing items change
- Comment - Notify when a new comment is posted
- You can select one, two, or all three (default: Created + Updated)
For Updated events: Choose what should trigger notifications.
- Page rules: Title and/or Content edits
- Database rules: Property changes and/or Content edits
- Database rules: Select properties to narrow updates, or leave empty to watch all properties → Property filter reference
- Databases with a Status property: Optionally filter by Status (when Status is selected)
🧮 Formula updates

Formula-only recalculations do not trigger real-time notifications. If you need time-based formula alerts, use Scheduled Alerts.
(Optional - Task databases only) Enable quick action buttons for status changes and self-assignment → Quick actions guide

ℹ️ Quick Actions Require Task Database

To enable interactive buttons, first connect your database as a task database on the Tasks page. Regular notifications work fine without this.
(Optional) Select fields to display in Discord notifications
(Optional) Toggle Discord mentions to control whether @mentions ping users (mentions still display when off)
Click "Create Rule"

Test it: Create or update a database item or page that matches your rule - the notification should arrive in Discord within a few minutes.

⏱️ Important: Notification Timing

Notifications typically arrive within around 1 minute (or faster), but can take up to 5 minutes (sometimes longer). This is how Notion's webhook system works - it batches rapid changes to avoid overwhelming your Discord channel. If a notification doesn't appear after 5 minutes, check the Notifications page for delivery status.

What You'll See

📬 Notification Contents

Page/task notifications: notification line, page/task title, page/task body excerpt, selected properties, and optional quick actions
Comment notifications: comment notification line, page/task context, and the actual comment text (attachments are not included)
Page/task body excerpt and people fields can render linked users as Discord @mentions; pinging depends on the Discord mentions toggle
Database properties (if selected - Status, Assignee, Due Date, Priority, etc.; people fields can @mention linked users)
Quick action buttons (task databases only, if enabled)

🔕 No Self-Pings

The person who triggered the change is excluded from pings, even if they appear in people fields or are mentioned in content.

Source Types at a Glance

Capability	Task database	Page database	Standalone page
Setup requirement	Database must be connected as a task database on the Tasks page	Any shared database can be used	Share the page with NotiCord
Events	Created, Updated, Comment	Created, Updated, Comment	Created (subpages), Updated, Comment
Property filters	All properties (default) or selected properties	All properties (default) or selected properties	N/A (Title is a toggle)
Status filtering	Available when the database has a Status property and Status is selected	Available when the database has a Status property and Status is selected	Not available
Quick actions	Status change buttons and optional "Assign to me" (if Assignee is mapped)	Not available (read-only)	Not available (read-only)
Subpages	Not applicable	Not applicable	None, direct children, or all descendants

Common Scenarios

Scenario	Event	Watch/Filter	Quick Actions	Result
New Task Inbox	Created	N/A	Status + Assign	All new tasks → #task-inbox with buttons
Completion Alerts	Updated	Status → Done	None	Status changes to Done → #wins (read-only)
Blocker Alerts	Updated	Status, Priority → Blocked	Status + Assign	Blocked tasks → #urgent with buttons
Documentation Updates	Updated	Content	None	Content edits → #docs (read-only)
Comment Alerts	Comment	N/A	None	New comments → #discussion (read-only)
Subpage Alerts	Created (subpage)	Subpages: Direct children	None	New subpages → #docs (read-only)
Multi-Channel Fan-Out	Created	N/A	Mixed	One event → multiple channels

Troubleshooting

Not receiving notifications? See the Notifications Not Working troubleshooting guide for common problems and solutions.

On the rules list, blocked rules show compact per-issue cards (for example, Notion source unavailable and Discord permissions missing) with dedicated fix links. Plan capacity is shown inline in the subtitle (for example: 2/2 configured · Plan limit reached), and the subtitle plus New Rule button state update immediately after creating or deleting a rule.

In the rule editor, message fields are split into two explicit sections:

Message Content (for page/task notifications)
Message Content (for comment notifications)

Notification History now shows your full notification-attempt history in paged results (50 per page with Load More) instead of a 7-day window.

If a database used by an existing rule is later deleted in Notion or unshared from NotiCord, the rules list and edit form show a Notion source unavailable warning. That rule will not trigger until you select an accessible database and save.

Guides