Notifications
Notification rules send matching Notion changes to Discord automatically.
Pick the right source
| If you want to watch | Choose this source | Best fit |
|---|---|---|
| Any currently shared page in the workspace | All pages | A fast first rule or broad workspace updates |
| One database or data source | Database items | Structured setups with filters, watched properties, and quick actions |
| One standalone page and its page tree | Selected pages | Docs areas, project hubs, or nested page collections |
Build your first rule
- Open Notifications.
- Click Create notification rule.
- Choose the source, destination, and Real-time delivery.
- Pick the event types you care about.
- Start the card with the title and one or two fields people actually need.
- Save the rule and make one matching change in Notion.
Allow a little time
Most notifications arrive within about 1 minute, but some take up to 5 minutes or longer because Notion batches updates.
Choose real-time or grouped sends
| Choose | When it fits best |
|---|---|
| Real-time | Each matching change should show up as its own Discord card |
| Scheduled changes | You want one grouped summary of what changed since the last run |
Keep the card useful
- Start with the title and one or two fields people care about most.
- Add more properties only when they help someone decide what to do next.
- Use quick actions only on database-backed rules where someone is likely to update the item from Discord.
Common gotchas
Direct-message rules send to one fixed linked person, not whoever edited the page. Comment notifications still need the page or database to stay shared with NotiCord. If you want a timed snapshot of what matches right now instead of recent changes, use Scheduled Summaries.
Need exact rule behavior? Open Notification Rules. If notifications are blocked, use Notifications are not sending.