A change-detection system is only useful if it catches the changes that matter and stays quiet about everything else. For a solo operator, reviewing noisy alerts can cost more than checking the sites by hand.

What actually happened

On 16 November, Perplexity launched Monitor API. A monitor works in one of two ways:

  • Topic monitors follow a broad subject through web search.
  • Page monitors watch up to ten URLs for text changes and return text diffs after an initial baseline.

Monitors run on a schedule and send qualifying updates to your application through a signed webhook.

Before forwarding web results, Perplexity's Decider checks freshness, relevance, source legitimacy and novelty. Developers can define a goal, adjust decision thresholds, pause or resume a monitor, and run a check on demand.

Pricing: web monitors cost $1 per 1,000 successful runs, and page monitors cost $1 per 1,000 URLs fetched. A run is not necessarily the same as a single page fetch.

Why a small team cares

Consider a solo automation consultant following release notes from ten platforms used in client integrations. A useful alert flags a removed API field, a pricing revision or a permission change, with enough source context to decide whether any workflow needs attention.

That is worth more than another daily list of vaguely related headlines.

An n8n webhook is a straightforward destination. Store the source, the detected change and the confidence information, then queue only relevant items for review. The saving is fewer scraping jobs to maintain and fewer false alarms to triage, not an impressive low per-run price.

Hype vs useful

Perplexity's freshness and relevance claims come from its own evaluation. They do not prove it will beat your existing system on your sources. Several things can change what it catches:

  • Page structure and redirects
  • Inaccessible content
  • Threshold settings

Signed delivery and automatic retries make the integration more reliable. They do not guarantee meaningful alerts.

Run a narrow test. Keep the old feed running alongside Monitor until it proves it catches material changes without adding review work. Do not connect an unreviewed monitor directly to client notifications or publishing.