Scheduled Summaries
Rules, limits, and edge cases for scheduled summaries.
Sources
| Source | What to know |
|---|---|
| All pages | Basic page fields and filters only |
| Database items | Full filters, row mentions, and quick actions |
| Selected pages | Basic page fields and filters only |
If a saved source later disappears or becomes unshared, the summary stays visible with a warning or paused state so you can repair it.
Filters and layout
- Filters check the current state of the item when the run happens.
- Database summaries support property-aware filters.
- All-pages and selected-pages summaries support only basic page filters on Title, Created by, and Last edited by.
- Summary content controls the list people see first.
- Summary item details controls the card opened from Details.
- If the list includes Details, choose at least one details field before saving.
Mentions and quick actions
- Database summaries can render row mentions from visible People fields.
- Channel-delivered summaries can also add fixed Additional mentions.
- Quick actions appear only on database-backed summaries and only on the summary item details card.
Cadence, timing, and limits
| Plan | Scheduled summaries | Cadence |
|---|---|---|
| Solo | 1 | Daily only |
| Team | Up to 3 | Daily or hourly |
| Pro | Up to 10 | Daily or hourly |
- Daily runs once during the chosen hour in the chosen timezone.
- Hourly runs once per hour.
- Moving a daily summary later to an hour that has not happened yet can trigger another run the same day.
Delivery behavior
- Each run rebuilds the summary from the items that match right now.
- A posted summary can show up to 10 matching items in one Discord message.
- If Only send when there are results is off, NotiCord can still send a message that says nothing matches right now.
- The in-app preview is read-only and uses the current draft.