Notifications
Use notification rules for changes someone should act on in Discord. A good rule answers three questions: what changed, who needs to see it, and what should they do next. Use Scheduled Summaries when the team wants a fresh list of what matches right now.
Docs, onboarding updates, and pricing changes are ready to share.
✏️ Amelia updated item Status
April launch notesDocs, onboarding updates, and pricing changes are ready to share.
Build one useful rule
- Open Notifications and click Create notification rule.
- Name the rule so history and troubleshooting messages are recognizable later.
- Choose the source and destination: broad workspace activity, one database workflow, one page tree, a team channel, or one fixed member DM.
- Start with Real-time unless the team wants one grouped digest. Choose the events, then use What should it show? to keep only the fields people need for the next step.
- Click Create rule, then make one matching Notion change.
Need to pause setup? Save draft keeps the rule silent. Drafts reserve a rule slot, but they do not send, schedule, appear in history, or appear in the public API.
Choose the source
| Source | Best for | Unlocks |
|---|---|---|
| All pages | Broad workspace activity | Fast first rule; filters can use Title, Created by, and Last edited by |
| Database items | Property-driven workflows | Rich filters, watched properties, database properties on cards, and Status/Select/People actions |
| Selected pages | One page, one database item page, or one page tree | Can include only the selected page, only child pages, or both; child databases inside the tree can match too |
Use Database items when a property should decide whether the rule sends. Filters are checked when NotiCord is ready to send, not at the instant Notion first reports activity.
Choose when it sends
| Delivery | Best for | Events it can watch |
|---|---|---|
| Real-time | One Discord card per matching change | New, updated, and deleted pages or items, plus comments |
| Scheduled changes | One grouped list of changes since the last run | New, updated, and deleted pages or items; comments are real-time only |
Scheduled changes can run daily, weekly, or hourly. Hourly requires Team or Pro. Use Scheduled Summaries when the team needs a current snapshot of matching pages or items instead of a change log.
Scheduled changes send a list first. Shown in each row becomes the list columns, Details button adds per-item buttons, and Additional mentions adds a Mentioning line for channel rules.
🔔 Launch review changes
Mentioning: @Launch Team
Configure the Discord card
NotiCord controls the main Discord card sections and spacing. In Notification content, you choose the useful parts: fields, language, extra pings, and update-card toggles. Drag selected property field chips to change the order of property rows on the card.
✏️ Amelia updated item Status
Refresh pricing screenshotsNew billing layout is live. Capture final shots before launch.
Mentioning: @Launch Team @Amelia
| Setting | Use it for |
|---|---|
| What should it show? | Pick the card line, title/link, content, and database fields. Comment events use their own picker. |
| Card language | Localize NotiCord system text and dates on Discord cards and previews. |
| Call this a | Built-in labels follow Card language. Custom labels stay as typed. |
| Additional mentions | Add a Mentioning line to channel-rule cards. Direct-message rules do not use it. |
| Ping people in Discord | Decide whether linked Notion users in visible People fields actually ping. Scheduled lists need that field. |
For update cards, More options may also show Show only changed properties and content, Show empty properties, and Include uploaded files. These toggles only appear when the selected source, events, and fields make them usable.
Configure matching
Use filters and watched properties for different kinds of noise control:
- Filters decide whether the item still matches before the rule sends.
- Notify only when these properties change narrows database update notifications to specific supported properties.
- Content changes and Property changes decide what counts as a real-time update.
Real-time watched properties do not support formula or rollup properties. Scheduled changes support a broader set, including formula fields, because they compare the saved run state instead of reacting to Notion's live property-change signal.
Scheduled-change content
Scheduled changes have two Discord surfaces:
- The list card uses Shown in each row for columns such as Title, Change, Details button, and database properties.
- The opened details card appears only when Details button is selected. Changed item details uses the same field picker and display toggles as real-time card details.
- Quick actions are available on scheduled changes only when Details button is selected, because actions live on the opened details card.
Quick actions
Quick actions are configured separately from notification content. Add comment and Upload files work as page actions. Status, Select, and People actions require Database items so NotiCord knows which database property to update.
Buttons appear as individual Discord buttons. Dropdown actions are for database Status or Select options and require a selected database.
If notifications are blocked, use Notifications are not sending. If quick actions are missing or failing, use Quick actions are missing or failing.