New-Item Alerts vs Page-Change Alerts: Which Should You Use?

NotiFast has two website-monitoring modes, and choosing the wrong one can produce irrelevant alerts or miss the change you intended to watch.

Use /notify-new-items when a page gains another listing, result, vacancy, article, or other repeated item. Use /notify-content-update when text inside an existing part of a page changes, such as a displayed price or availability label. Both modes are documented in the NotiFast setup guide, but their setup previews work differently.

Before you begin, invite NotiFast using the link in its documentation. The person inviting it needs Manage Server permission. The invitation must include the Applications Commands scope for slash commands, and the destination channel must allow the bot to send messages and embed links.

The short decision guide

The key question is whether the thing you care about is a new repeated item or a change inside an item that already exists.

Choose /notify-new-items for growing lists

New-items monitoring is designed for pages containing repeated entries. Typical examples include marketplace searches, job-board results, release lists, and category pages.

A concrete example is a filtered marketplace search for used cameras under a chosen price. You are not asking whether the current first result changes its wording. You are asking whether another matching listing appears. That is a new-items problem.

Options available during setup

Run /notify-new-items in Discord and provide:

• name: a recognizable name for the monitor.
• url: the page containing the list you want to watch.
• items-limit: an optional limit on how many detected items are included in a run's outgoing alerts.
• channel: an optional destination; if omitted, the current channel is used.
• tags: optional comma-separated labels.

For example, you could name the monitor used-camera-search, paste the filtered results URL, and select a dedicated deals channel.

Inspect the candidate-set preview

The command scans the page before saving the monitor. Its preview shows an example of the notification image and link it identified.

Check three things:

1. Is the wanted listing inside the current set? If not, use Next set to inspect another candidate container.
2. Does each selected type represent the repeated items you want? Deselect an unrelated type if the preview includes navigation cards, recommendations, or another repeated block.
3. Does the example open the right item URL? If the interface offers another candidate link, cycle through it before saving.

The preview explicitly advises that the correct image should contain one item. Treat that as an inspection step, not as proof that every future page state will be parsed correctly.

When the set, item types, and example link look right, select Save. If setup reports that no container was found, the scanner did not identify a usable repeated-item container on that attempt.

Choose /notify-content-update for an existing value

Content-update monitoring is for a value or message already present on the page. A product price, stock label, event status, or release note heading can fit this mode.

Suppose a product page currently contains €249.00, and you want to know when that displayed text changes. The product is not a new item in a growing list, so /notify-content-update is the appropriate starting point.

Options available during setup

Run /notify-content-update and provide:

• name: a recognizable monitor name.
• url: the page containing the text.
• search-text: required text used to locate the candidate element.
• track-all-changes: an optional switch that broadens monitoring to changes in the selected container. If it is not set, monitoring is limited to the search text.
• channel: an optional destination that defaults to the current channel.
• tags: optional comma-separated labels.

For the example above, copy text that currently appears on the page. The command requires search-text to exist on the site and to be one line. If it cannot find that text, it cannot present a candidate element for saving.

Inspect the element preview

The content-update preview shows the whole text of a candidate element and emphasizes the supplied search text. If the first candidate is not the price or status block you intended, use Next element until the correct one appears.

Before selecting Save, ask:

• Does this element contain the value I care about?
• Does it also contain timestamps, rotating messages, counters, or other text that changes for unrelated reasons?
• Do I actually need track-all-changes, or is tracking the supplied text enough?

Leave track-all-changes off when the target text alone represents the decision you care about. Turn it on only when changes elsewhere in the selected container are also meaningful. Broad monitoring can be useful, but it gives more surrounding content a chance to trigger an alert.

What happens after a content-update monitor runs

A content-update run compares the current text with the previously stored text. A no-change result is recorded without sending a change message. When a change is found, the newly observed text becomes the stored previous value for the next comparison, and the notification presents the old and new content.

This has two practical consequences:

1. The setup preview matters because it determines which candidate element becomes the subject of later comparisons.
2. A notification means that monitored text changed; it does not by itself mean the price decreased, the product became available, or the change was favorable.

Review the old and new content before acting. NotiFast monitors and reports changes; this workflow does not buy products, place bids, or evaluate whether a deal is worthwhile.

When you need both modes

Some tasks contain two different questions.

Imagine a clearance category page where new products appear, followed by a product page whose price may change:

1. Use /notify-new-items on the category or filtered-results URL to detect newly added products.
2. Create a separate /notify-content-update monitor for a specific product whose displayed price or availability you want to follow.

Keeping those jobs separate makes each notification easier to interpret. The first says a new entry was detected. The second says text in an existing selected element changed.

NotiFast monitors one URL per monitor, so watching several product pages requires a separate monitor for each URL.

How to reduce avoidable noise

Keep the page scope explicit

Each monitor watches one URL. Decide which page answers your question before creating the monitor; watching several pages requires separate monitors.

Choose the narrowest useful preview

Distill’s false-alert guide identifies timestamps, ads and counters as common sources of noise and recommends focusing on essential content. That supports the general selection principle here; it does not mean NotiFast has Distill’s delay, selector or condition controls.

For new items, select the candidate set and item types that represent the repeated entries. For content updates, choose the candidate element that contains the wanted text without unnecessary surrounding content.

Do not use content updates as a threshold rule

/notify-content-update detects changed content. The supplied setup does not establish a rule such as “alert only below €200.” If €249.00 changes to €259.00, that is still a content change. Interpret the old and new values in the notification.

Review history before changing the monitor

Use /history to inspect scan history and /info to view active-monitor details. If the target URL or settings need adjustment, use /update-job. Remove a monitor you no longer need with /remove-job.

Do not assume a shorter schedule guarantees that an alert will arrive before an item sells or a page changes again. Check timing is only one part of the path; the page must also be reachable and expose the relevant content when a check runs.

Setup checklist

Before saving a monitor, confirm:

• You chose new items for an expanding list or content updates for existing text.
• The URL is the exact page you intend to monitor.
• The preview shows the correct candidate set or element.
• New-item examples link to the intended item pages.
• search-text is present and on one line for content updates.
• track-all-changes is enabled only when surrounding container changes matter.
• NotiFast can send messages and embed links in the destination channel.

If the preview cannot identify the right content, do not save the monitor merely to complete setup. For content updates, check that the supplied search text is actually on the page and is one line. A no-container or item-not-found result tells you setup did not identify a usable candidate on that attempt; it does not diagnose why. These commands do not establish universal site compatibility.

Open the NotiFast documentation to add the bot and create the monitor in the Discord channel where you want alerts.