Get Notifications in Discord

Use notification rules when you want Notion activity to appear automatically in a Discord channel or in one linked user's Discord direct messages.

Before you begin

1. Share the pages or databases you want NotiCord to watch with NotiCord in Notion.
2. Decide whether the rule should send to a shared Discord channel or one linked account by direct message.
3. If you want a channel destination, make sure the bot can send notifications in that channel. Required permissions: View Channel, Send Messages, Embed Links, Attach Files, and Send Messages in Threads.
4. If you want a direct-message destination, make sure that account is already linked in Account Linking.

If a database or page is missing in a picker, use Give NotiCord Access in Notion.

Create a rule

1. Go to Notifications in the sidebar
2. Click Create notification rule
3. Start from the default rule name, Notification rule, or rename it
4. Leave the default All pages source, or switch to Database items or Selected pages
5. If you choose Database items or Selected pages, pick the Notion source
   • All pages watches any currently shared page in your connected NotiCord workspace.
   • Database items watches items inside one database.
   • Selected pages watches one chosen page and, by default, the pages inside it too.
   • Selected pages also lets you choose whether to watch the selected page only, child pages only, or both. New selected-page rules start with the selected page and child pages.
6. Choose Discord channel or Direct message
   • Discord channel sends to the selected shared channel
   • Direct message sends to one fixed linked account that you choose explicitly
7. Choose When to send
   • Real-time sends notifications when Notion sends new activity and usually arrives within 1 to 5 minutes
   • Scheduled changes checks the selected source on a schedule and groups matching changes into one notification per run
8. Choose which events should send notifications
   • All pages and Database items rules: New items, Item updates, Comments
   • Selected pages rules: New subpages, Page updates, Comments
9. If you enable Item updates or Page updates, choose the matching update types
   • All pages and Database items rules: Property changes and/or Content edits
   • Selected pages rules: Title changes and/or Content edits
10. Optional: for database rules with Property changes, narrow the rule further

• Inside Notify when, Only when these properties change controls which changed properties can trigger the notification

• Leave it empty to notify on any supported property change

• Supported real-time trigger properties are Title, Text, Number, Date, Checkbox, Email, URL, Phone number, Status, Select, Multi-select, People, Files, and Relation

• The changed-property picker now shows non-metadata properties instead of silently hiding unsupported ones

• Formula stays visible there with a Scheduled only badge and a note that scheduled notifications support that field

• Rollup stays visible there with a Not supported badge instead of disappearing from the picker

• The separate Advanced filters section adds saved filter rows such as Status, Select, People, Checkbox, Number, Date, Relation, Formula, and text checks

• People filters can either choose a workspace user or use Contains to match the visible Notion person name, which is useful for external collaborators

• Relation filters can now match one specific related page by searching the linked related database, not just whether the relation is empty

  • Files and Rollup stay visible in advanced filters with a Not supported badge
  • That section starts collapsed until you add filters
  • Each filter row is combined with AND

11. If you choose Scheduled changes, set the schedule and change check

• Choose Daily or Hourly (Team only)
• Choose New items, Item updates, or both on All pages and Database items, or New subpages, Page updates, or both on Selected pages
• On Database items, watched properties are optional when updates are enabled. Leave the picker empty to match any supported property change, or choose properties to narrow it.
• Supported scheduled watched-property types are Title, Text, Number, Date, Checkbox, Email, URL, Phone number, Status, Select, Multi-select, People, Relation, and Formula
• Files and Rollup do not count for scheduled watched-property matching
• On All pages and Selected pages, scheduled changes stay page-generic. You can choose the notification list row fields and changed item details fields, but advanced filters, watched-property selection, quick actions, and row mentions stay unavailable because those sources do not use one database schema.
• Choose the row fields you want for the notification list. Add Title if you want the item title shown in the list, and choose at least one row field before saving or previewing the notification list.
• Choose the changed item details fields used after Details. New scheduled rules start with Notification line, linked title, and page or item content selected. If the notification list includes Details, choose at least one details field before saving or previewing that card.
• On Database items, optional: adjust or remove the quick actions for the changed item details card. If the database has supported properties, the first button row is added automatically.
• On Database items, optional: turn on row mentions so visible People fields render as Discord mentions in the notification list

12. Optional: customize the notification rule name, notification wording, mentions, quick actions, or card language

• All pages and Database items rules can call it Page, Task, Item, or Custom...
• Selected pages rules can call it Page or Custom...
• New All pages rules start with Page wording. Database items rules still start with Item wording, and you can switch either one to Page, Task, or Custom... when that reads better for the rule.
• Compatible database rules add the first quick-action button row automatically when supported quick actions are available
• All pages and Selected pages scheduled rules do not support quick actions, advanced filters, watched-property selection, or row mentions because they do not point at one database schema
• Quick actions on real-time database rules are available only for shared-channel notifications
• Scheduled-change quick actions appear on the changed item details card for database rules and work in both shared channels and direct messages
• Quick actions can mix button rows and dropdowns. Button rows can mix supported properties, while each dropdown uses one status or select property
• Channel rules can add fixed Additional mentions inside Notification content
• Additional mentions stay fixed for the rule. They do not automatically follow the current assignee.
• Custom uses one singular name such as issue, release note, 問題, or 🚀 release
• Custom labels can use any short single-line text, including non-English words and emoji
• Discord mentions such as @everyone and <@123> are not allowed in custom labels
• Scheduled-change rules use the saved wording and card language on both the notification list and changed item details cards, including the in-app preview and Send preview
• Card language can be English (US), Português (Brasil), Español, Polski, Français, 日本語, Deutsch, 한국어, 繁體中文, Italiano, Bahasa Indonesia, Türkçe, or Nederlands
• Card language only affects Discord notification cards, Send preview, and the in-app notification card preview
• Notion-authored content, property names, status/select option names, and your custom label are not translated
• Custom wording only changes the singular label used in the notification line

13. Save the rule. NotiCord returns you to the notification rule list.

Preview it: real-time rules try to show one real in-scope page or item from that source in the preview. You can switch the sample from the preview dropdown, but only to other in-scope pages or items for that rule. If no real sample is available yet, preview falls back to example content. Scheduled changes show two live previews for the current draft: Notification list and Changed item details. The list preview uses the pages or items that currently match that setup, and the Changed item details preview lets you switch between those sample pages or items. When the preview refreshes because you change the sample or current draft, the current card stays visible with a loading indicator on top. The in-app preview is read-only, so buttons and links work only in Discord. When content files are enabled, the editor preview shows the same attachment tiles as the live card. Send preview sends the current draft preview to the selected destination. Preview can still show Discord mention formatting, but it never pings anyone, sent real-time preview notifications use the same live quick actions, footer, and media/file rendering as the current draft, scheduled-change detail previews and live Details cards upload the same supported PDFs/files as the current draft when those files are available, scheduled-change list previews still keep Details buttons disabled, structured page body content such as toggle text, callouts, numbered items, and small tables stays in the card when it fits, small tables render as aligned Discord tables with up to 5 rows and up to 3 source columns plus an ... overflow column when more columns exist, preview explains missing required displayed-field selections instead of showing a generic invalid card, and preview does not confirm that a future Notion change will match the rule.

Need help while setting it up? Use Ask for help in the preview header to open the in-app support form.

Test it: create, edit, or comment on something that matches the rule. If you kept All pages, any matching activity on a currently shared page can trigger the rule.

You can save a rule or send a notification preview only after the selected destination is ready. Channel rules need a working Discord channel with the required bot permissions. Direct-message rules need one linked account, and Discord must allow NotiCord to message that person.

If Discord reports a deterministic delivery problem, such as a deleted target channel, lost bot access/permissions, an unlinked DM account, or a user whose DMs are unavailable, NotiCord pauses the rule automatically. Fix the destination setup, then turn the rule back on from the notification rule list.

What users often miss

• New subpages on a page rule means a new subpage under that page, so the page scope must include child pages.
• Selected pages scheduled rules keep the same page scope semantics as real-time rules: selected page only, child pages only, or both.
• All pages rules default to Page wording, Database items rules default to Item, and Selected pages rules default to Page. Database-item and all-pages rules can also use Page wording when that matches the content better. A custom label changes text only and does not enable Discord Commands or alter quick actions.
• On database rules that watch item updates, changed properties and advanced filters do different jobs. Changed properties decide which edits wake the rule up. Filter rows check the item's latest values before NotiCord sends the notification.
• The selected properties picker in Notification content includes non-metadata database properties such as Files, Formula, and Rollup. The title field still uses the dedicated title options.
• URL properties in Notification content show as clickable links, and relation properties show linked related-page titles when NotiCord can resolve them.
• Rule history reuses the rule's configured singular label when available, but history itself stays in English even when the Discord card language is something else.
• Formula recalculations do not trigger real-time notifications, but scheduled changes can still watch formula fields.
• Rollup recalculations do not trigger real-time notifications, and scheduled changes do not support rollup watched properties.
• The preview on the rule page matches the live Discord wording, card language, visible fields, content media/file choices, and quick-action visibility for the selected rule. Real-time rules use a real in-scope page or item when possible and let you switch samples. Scheduled changes use live Notification list and Changed item details previews for the current draft.
• The in-app preview is read-only. Buttons and links work only in Discord.
• If preview is blocked because a required displayed-field selection is empty, the preview rail explains which field selection you still need to choose.
• Send preview works on the current draft. You do not need to save the rule first, and the preview notification does not appear in rule history.
• When content files are enabled, the in-app preview shows the same attachment tiles as the live card.
• Sent real-time preview notifications use the same footer, quick actions, and media/file rendering as the current draft live card, but still suppress pings.
• Scheduled-change detail previews and live Details cards upload the same supported PDFs/files as the current draft when those files are available.
• Scheduled all-pages and selected-pages previews are page-generic, so they do not show database-only watched-property summaries, filters, quick actions, or row mentions.
• Scheduled-change preview shows current matching rows for the draft, not the exact future delta set. The real scheduled run still sends only changes since the last run.
• Item updates, Page updates, and Comment previews can still use simulated event text when NotiCord cannot prove a recent matching update or comment, even if the page or item content is real.
• The person who triggered the change is never pinged, even if they appear in people fields or content.
• A direct-message rule sends to one fixed linked account per rule. It does not follow assignees, mentions, or whoever triggered the change.
• Switching a rule to Direct message does not pick a linked account for you. Choose the recipient explicitly before saving or sending preview.
• If you switch a real-time database rule to Direct message, quick actions are hidden because real-time DM rules do not support them yet.
• Page or item content is adapted for Discord instead of recreating the full Notion layout. Text stays in reading order, and you can choose whether images/direct video files render inline and whether downloadable PDFs/files render as attachment tiles at the bottom of the card.
• Structured page bodies keep toggle text, callouts, numbered items, and small tables when they fit. Small tables render as aligned Discord tables with up to 5 rows and up to 3 source columns plus an ... overflow column when more columns exist. Very long page bodies are still trimmed to fit the Discord card.
• If the page body preview cannot be read in Notion, the notification still sends and history shows Sent with warning.
• If a rule is auto-paused, NotiCord sends one warning email when warning notifications are enabled in Email Preferences. You can open that page from Account Settings or from the footer links in NotiCord emails.

Use Notification Rules Reference for full option-by-option behavior, Quick Actions for button setup, and Notifications Not Working when a rule does not send notifications.