Get an alert when a web page changes, set up from ChatGPT or Claude
Ask your assistant to watch a page. ClickRuntime checks it on a schedule, compares it with the last version it saw and sends you a short summary of what changed, by email or in Slack.
- When
- Every hour at :15
- Uses
- acme.com, Email to you
- 11:15✓ Acme pricing page watch · SucceededLast run11:15 · no change
Can ChatGPT or Claude watch a website for changes?
Not on their own: an assistant only acts while you are chatting, and it doesn't remember what the page looked like last time. With ClickRuntime connected, you ask once and it sets up an automation that checks the page on a schedule (every 5 minutes or slower), keeps the last version, and emails you or posts to Slack only when something changed.
Why the assistant can’t do this on its own
- No schedule. ChatGPT and Claude answer when you send a message. Nothing checks the page at 3 a.m. unless something outside the chat runs it.
- No memory of the page. To know something changed you need the previous version. A chat starts fresh, so there is nothing to compare against.
- Built-in scheduled tasks re-run a prompt and answer in the chat. They can browse, but they don't keep a stored copy to compare against, can't use your Slack workspace, and have limits on how many run.
- ClickRuntime runs a small Python script on its servers. It fetches the page, keeps a fingerprint and a copy of the part you care about in the automation's state, and only notifies you on a real change.
Set it up from your AI assistant
The same steps work in ChatGPT, Claude, Cursor and any assistant that supports MCP connectors.
- Step 1Connect ClickRuntime to your assistantAdd ClickRuntime as a connector (MCP server) in ChatGPT, Claude, Cursor or another MCP client, using https://clickruntime.com/api/mcp. You sign in with Google or email; there is no API key to copy. This is done once per assistant.
- Step 2Paste the promptStart a new chat and paste: “Create a ClickRuntime automation: every hour, check https://acme.com/pricing. Only look at the pricing table, not the whole page. When it changes, email me a short summary of what changed. Don't email me when nothing changed.” Change the details (times, channels, addresses) to yours.
- Step 3Read the draftThe assistant restates what will happen, asks for anything missing, such as your timezone or which channel to post to, and saves a draft automation. A draft never runs on its own, so nothing happens until you agree.
- Step 4Connect accounts and save keysWatching a public page needs no accounts. Email alerts go to the address you signed in with. If you'd rather get the alert in Slack, the assistant gives you a button to connect a Slack workspace for notifications in the ClickRuntime dashboard, and asks which channel to use.
- Step 5Test itThe assistant runs it once. The first run stores the current version and reports “baseline saved”. To see an alert, it can run a test against a page you know will differ, or you can ask it to show what the summary would look like from the stored copy.
- Step 6Turn it onThe assistant tells you what will run, when, and which services it will contact, then asks your permission to turn it on. From then on it runs on ClickRuntime's servers, and you can close the chat.
- Step 7Check it in the ClickRuntime dashboardThe automation's page shows its schedule, the next three run times and every run with its result, such as “no change” or “changed: Pro plan price $49 → $59”. Under State you can see the stored fingerprint and when it last changed. Pause, run now and the script itself are on the same page.
“Create a ClickRuntime automation: every hour, check https://acme.com/pricing. Only look at the pricing table, not the whole page. When it changes, email me a short summary of what changed. Don't email me when nothing changed.”
Connector setup for each assistant: ChatGPT, Claude, Claude Code, Cursor, and other assistants.
What the assistant writes
A typical script for this job. Yours matches your pages, accounts and wording, and you can read every version in the ClickRuntime dashboard.
- Only the selected part of the page is compared, so a rotating banner or a timestamp in the footer doesn't cause false alerts.
- The first run stores a baseline. Every later run compares against the last stored version, which lives in the automation's state.
- A check that finds no change returns straight away. Quick checks that find nothing and send nothing aren't counted toward your monthly runs.
- The AI summary uses ClickRuntime's built-in model, with no API key, including on the free plan. If AI isn't available the alert still goes out with a plain message.
A schedule, not a trigger link
Use a schedule. A web page doesn't tell anyone when it changes, so the automation has to look. Hourly suits most pages; every 5 minutes is the shortest interval, for things like a stock or ticket page.
If the site does send webhooks (for example a CMS that posts on publish), use the automation's trigger link instead and the check runs only when something was published.
Limits
- The shortest interval is every 5 minutes.
- Pages are fetched over HTTPS without a browser, so content drawn by JavaScript after load may not be in the HTML. Ask the assistant to use the site's JSON endpoint or API if there is one.
- Pages behind a login work only when the site offers an API or token you can save as a secret in the ClickRuntime dashboard.
- Respect the site's terms and robots rules, and don't check more often than you need.
Troubleshooting
The run fails with “selector not found”.
The page's layout changed or the part you watch is drawn by JavaScript. Ask your assistant: “my page watch can't find the table, fix it”. It reads the run's error and updates the selector.
I get alerts for changes that don't matter.
Narrow what is compared, for example only the price cells, or ask the assistant to ignore dates and counters before comparing.
The site returns 403.
Some sites block automated requests. Check whether the site has an API or feed, and use that instead.
What you can add next
The first version is rarely the last. Because the automation is a Python script with memory, AI and any API available, you grow it by asking your assistant for the change. Each change is a new version, and a failed deploy never replaces the working one.
- Built-in AI
Only alert when the change matters, judged by AI against what you care about
“Change my pricing page watch so it only emails me when a price or plan limit changes, and ignores wording and layout changes.”
- Memory between runs
Keep a history of every version and when it changed
“Change my pricing page watch so it keeps the last 20 versions with their dates, and include the date of the previous change in each alert.”
- Multi-step logic
Watch several competitor pages in one automation
“Change my pricing page watch so it also checks the pricing pages of beta.com and gamma.io, and says which site changed in each alert.”
- Any app or API
Post changes to a Slack channel instead of email
“Change my pricing page watch so it posts each change to #competitors in Slack instead of emailing me.”
- Any app or API
Log every change as a row in a Google Sheet
“Add to my pricing page watch: when it finds a change, add a row to my Competitor changes sheet with the date, the site and the summary.”
- Schedules
Check faster during business hours only
“Change my pricing page watch to check every 15 minutes on weekdays from 8:00 to 18:00 London time, and hourly otherwise.”
- Built-in AI
A weekly AI digest of everything that changed
“Add to my pricing page watch: every Monday at 9, email me one summary of all the changes from the past week.”
Questions about website change alerts
Can ChatGPT monitor a website for changes by itself?
Not reliably. ChatGPT only acts while you chat, and its scheduled tasks re-run a prompt without keeping a stored copy of the page to compare. Connect ClickRuntime and ChatGPT can set up an automation that checks the page on a schedule, keeps the last version and alerts you only on a change.
Can Claude watch a website for me?
Yes, through ClickRuntime. Add ClickRuntime as a connector in Claude, ask it to watch the page, and it sets up an automation that runs on ClickRuntime's servers after the chat is closed.
How often can it check?
As often as every 5 minutes. Hourly is enough for most pages and uses about 720 runs a month, but checks that find no change and send nothing aren't counted.
Does it work on pages that need JavaScript?
Pages are fetched without a browser. If the content is loaded by JavaScript, the assistant can usually call the JSON endpoint the page itself uses, or the site's API.
Is it free?
The free plan includes 250 runs a month, and checks that find nothing and send nothing aren't counted. The AI summary is included, including on the free plan.
What else can I add to it later?
Anything in the Extend it list on this page, such as watching several sites, logging changes to a sheet, or a weekly AI digest. Ask your assistant for the change and it updates the same automation.
Other use cases
Scheduled tasks in ChatGPT and Claude
“Create a ClickRuntime automation: every weekday at 9, fetch yesterday's orders from our Shopify store and post the total to #sales in Slack.”
See the use case →Run code every hour
“Create a ClickRuntime automation: every hour, check our public API's /health endpoint and Slack #alerts if it returns anything but 200.”
See the use case →Webhook automation
“Create a ClickRuntime automation: when someone submits our Typeform, add their answers to a message in #leads.”
See the use case →Cron jobs without a server
“Create a ClickRuntime automation: every night at 2am UTC, call POST https://api.example.com/tasks/reindex with my ADMIN_TOKEN and email me if it doesn't return 200.”
See the use case →AI agent automations
“Create a ClickRuntime automation: every morning at 8, summarize new GitHub issues labelled 'bug' on our repo and post them to #eng.”
See the use case →Monitoring and alerts
“Create a ClickRuntime automation: every 5 minutes, check https://api.example.com/health and Slack #oncall if it fails twice in a row.”
See the use case →Stateful automations
“Create a ClickRuntime automation: every hour, check this product page and email me only when the price drops below the lowest price you've seen.”
See the use case →AI triage and summaries
“Create a ClickRuntime automation: every 15 minutes, label new support emails as billing, bug or other and post billing ones to #billing.”
See the use case →Price drop alerts
“Create a ClickRuntime automation: every 2 hours, check the price on https://shop.example.com/products/monitor-27. Email me when it drops below $280. Tell me only once per drop, and include the lowest price seen so far.”
See the use case →Uptime checks
“Create a ClickRuntime automation: every 5 minutes, check https://app.example.com/health. It's down if the status isn't 200, it takes longer than 5 seconds, or the body doesn't contain "ok". After 2 failures in a row post to #ops in Slack, and post again when it's back up with how long it was down.”
See the use case →RSS feed alerts
“Create a ClickRuntime automation: every 30 minutes, check https://www.postgresql.org/news.rss. Post each new item to #eng in Slack with its title, link and a one-line summary. Never post the same item twice. On the first run, don't post old items.”
See the use case →Job post alerts
“Create a ClickRuntime automation: every 2 hours, check the Greenhouse job boards for the companies acme and betaco. Email me new jobs that are product design roles open to remote work in Europe. Include title, location and link. Never send the same job twice.”
See the use case →Brand mention alerts
“Create a ClickRuntime automation: every 30 minutes, search Reddit and Hacker News for "Acme CRM". Post each new mention to #mentions in Slack with the title, link and a label: question, complaint, praise or other. Never post the same thread twice.”
See the use case →Daily Slack message
“Create a ClickRuntime automation: every weekday at 9:00 Europe/Berlin, post to #team in Slack: a good-morning line, the number of open issues labelled Bug in our Linear team ENG, and the 3 oldest ones with links.”
See the use case →Daily news digest
“Create a ClickRuntime automation: every day at 7:30 Europe/London, collect new items from these feeds: <feed URLs>. Pick the 5 most important for someone following AI policy in the EU, and email me a digest with a two-sentence summary and link for each. Don't include anything I was sent before.”
See the use case →Weekly metrics to Google Sheets
“Create a ClickRuntime automation: every Monday at 7:00 America/New_York, add a row to the KPIs tab of my sheet “Company metrics” with the week start date, last week's Stripe revenue (succeeded charges minus refunds), number of new customers and number of refunds.”
See the use case →Morning briefing
“Create a ClickRuntime automation: every weekday at 7:00 Europe/Lisbon, read today's events from my work Google Calendar, get today's forecast for Lisbon, and email me a short briefing: the weather in one line, each meeting with time and who's in it, what I should prepare, and my free blocks of 30 minutes or more.”
See the use case →Slack channel summary
“Create a ClickRuntime automation: every weekday at 17:30 America/Chicago, read today's messages and thread replies in #product, and post to #product-digest a summary with three parts: decisions made, open questions, and action items with who owns them.”
See the use case →Inbox summary each morning
“Create a ClickRuntime automation: every weekday at 7:30 America/Los_Angeles, read the emails that arrived in my Gmail inbox since the last summary. Email me a summary in three groups: needs a reply, FYI, and newsletters or notifications. One line per email with the sender. Skip anything I already read.”
See the use case →Form submissions to Google Sheets
“Create a ClickRuntime automation: when someone submits my Typeform contact form, add a row to the Leads tab of my Leads spreadsheet with the date, name, email, company and message. Check the Typeform signature so only real submissions are added.”
See the use case →Form leads to your CRM
“Create a ClickRuntime automation: when my website form posts a lead (name, email, company, message), create or update the contact in HubSpot by email, set lifecycle stage to lead, and add the message as a note on the contact.”
See the use case →Handle Stripe webhooks
“Create a ClickRuntime automation: when Stripe sends checkout.session.completed, post the customer email and amount to #sales in Slack. Check the Stripe signature and handle each event only once.”
See the use case →React to GitHub events
“Create a ClickRuntime automation: when a new issue is opened in acme/app, read the title and body and add one label: bug, feature or question. Check GitHub's webhook signature.”
See the use case →Sort Gmail automatically
“Create a ClickRuntime automation: every 15 minutes, look at new messages in my Gmail inbox and add one label: Invoice, Customer, Newsletter or Needs reply. Email me straight away when a customer message sounds urgent.”
See the use case →Recurring reminders
“Create a ClickRuntime automation: on the last weekday of every month at 10:00 London time, post “Reminder: send this month's invoices” to #finance in Slack.”
See the use case →Stale pull request reminders
“Create a ClickRuntime automation: every weekday at 9:30 Berlin time, find pull requests in acme/app and acme/api that are not drafts, have been open more than 24 hours and have no review yet. Post them to #eng in Slack with the title, age, author and requested reviewers. Post nothing if there are none.”
See the use case →Scheduled social posts
“Create a ClickRuntime automation: every 15 minutes, read my Post queue sheet (columns: When, Text, Status). Publish each row whose When has passed and whose Status is empty to my LinkedIn profile, then set Status to the post link.”
See the use case →Sync data between apps
“Create a ClickRuntime automation: every 30 minutes, find records in my Airtable Customers table that changed since the last run, and create or update the HubSpot contact with the same email, copying name, company and plan.”
See the use case →Summarise customer feedback
“Create a ClickRuntime automation: every Monday at 9:00, read the rows added to my Feedback sheet since last time (columns: Date, Source, Text), group them into up to 6 themes with a count and one short quote each, and post it to #product in Slack.”
See the use case →Daily standup in Slack
“Create a ClickRuntime automation for our async standup: every weekday at 9:30 Berlin time, post “Standup: what did you do yesterday, what's next, anything blocking?” in #team. At 12:00, read the replies in that thread and post a short summary in the thread, listing blockers first and who hasn't replied.”
See the use case →
Set up your first automation in ChatGPT or Claude
Free plan. No credit card.