Schedule icon
Webhook icon
Get icon
Script icon
If icon
SlackIncomingWebhook icon
Log icon
Set icon

Watch a Page for Content Changes

Monitor any page for content changes using KV-persisted hashes and Slack alerts.

Categories
CoreInfrastructure

Competitor pricing pages, status pages of vendors, policy documents, a landing page before a launch — things you refresh manually today. This blueprint hashes the page on a schedule, persists the hash in the Kestra KV store, and only tells you when the hash actually moved.

How it works

  1. load_previous_hash (io.kestra.plugin.core.kv.Get) reads the last hash, tolerating a missing key on first run.
  2. fetch_and_hash (io.kestra.plugin.scripts.python.Script) fetches the page, normalizes whitespace, and emits a SHA-256 via the ::{"outputs": ...}:: protocol.
  3. compare_hashes (io.kestra.plugin.core.flow.If) alerts via alert_change only when a stored hash exists and differs; otherwise log_unchanged.
  4. store_new_hash (io.kestra.plugin.core.kv.Set) persists the fresh hash — this is what makes the schedule stateful.
  5. The errors block alerts Slack when the fetch fails.

What you get

  • Change alerts instead of a human refreshing tabs.
  • A last-seen hash in KV and in the execution history.
  • A page_hash output for downstream comparison steps.

Who it's for

  • Growth teams watching competitor pages.
  • Ops watching vendor status or legal-doc edits.
  • Anyone who has said "I'll just check it every morning".

Why orchestrate this with Kestra

A cron job that prints a hash goes nowhere. The flow adds state (KV), a branch (change vs not), an alert, failure reporting, and history — and the next step (snapshot diff, archive to S3, open a ticket) is one task away.

Prerequisites

  • The URL reachable from the Kestra Worker.
  • A Slack webhook.

Secrets

  • SLACK_WEBHOOK_URL: webhook for change and failure alerts.

Quick start

  1. Add the Slack webhook secret.
  2. Set url and a unique kv_key per watched page.
  3. Run twice — the second run should log "No content change".
  4. Enable watch_schedule.

How to extend

  • Diff the old/new body and post an excerpt in Slack.
  • Loop over a list of URLs, one KV key each.
  • Hash only a CSS selector region to ignore ads.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.