Get an alert when a price drops, set up from ChatGPT or Claude
Tell your assistant which product and your target price. ClickRuntime checks it on a schedule, remembers the prices it has seen and emails you once when it drops, not every time it checks.
- When
- Every 2 hours
- Uses
- shop.example.com, Email to you
- 14:00✓ Monitor price watch · SucceededLast run14:00 · $319, above target
Can ChatGPT or Claude track a price and tell me when it drops?
They can look a price up while you chat, but they can't keep checking afterwards or remember what the price was yesterday. With ClickRuntime connected, you ask once and it sets up an automation that reads the price on a schedule, stores each reading and emails you when it falls below your target.
Why the assistant can’t do this on its own
- A price drop is a change over time. Spotting one needs a check that keeps running and a record of earlier prices. A chat has neither.
- Built-in scheduled tasks re-run a prompt and reply in the chat. They don't keep a price history to compare against, so they either repeat the same answer or miss the drop.
- You want an alert once, not every two hours. That needs memory of whether you were already told, which lives in the automation's state on ClickRuntime.
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 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.” 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 keysA public product page needs no accounts. The email goes to the address you signed in with. If the shop has a price API that needs a key, the assistant sends you to the ClickRuntime dashboard to save it as a secret; it never asks for the key in chat.
- Step 5Test itThe assistant runs it once and shows the price it read, so you can check it matches the page. It can also run it with a higher test target to show the email you'd get.
- 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 dashboardEach run shows the price read and whether it was above or below target, for example “$319, above target”. State shows the lowest price seen and whether an alert was already sent for the current drop.
“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.”
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.
- The price is read from the page's structured data first, which is steadier than the visible layout. A CSS fallback covers shops without it.
- Plain code compares the number with your target. No AI is needed for a threshold, so no AI tokens are used.
- The alerted flag in state makes sure you get one email per drop, and resets when the price goes back up.
A schedule, not a trigger link
Use a schedule: shops don't send you a message when they change a price. Every few hours is enough for most products; flash sales may justify every 15 or 30 minutes. The shortest interval is every 5 minutes.
If you sell the product yourself and your store sends product-update webhooks, a trigger link is better than checking.
Limits
- Every 5 minutes is the shortest interval.
- Pages are fetched without a browser. If the price only appears after JavaScript runs, ask the assistant to use the shop's product JSON or API.
- Some large shops block automated requests or require their own product API. Check the shop's terms.
- Prices can differ by country and currency. The automation sees the price the shop serves to a server in the cloud.
Troubleshooting
The run fails with “No price found”.
The shop changed its page or loads the price with JavaScript. Ask your assistant to “fix my price watch” and it reads the error and finds another source, often the product's JSON.
The price it reads is in the wrong currency.
Ask the assistant to add the shop's country or currency parameter to the URL, or to convert with a currency API.
I never got an alert even though the price dropped.
Check the runs in the ClickRuntime dashboard: the price read is in each result. If an alert was already sent for an earlier drop, it waits until the price goes back above target.
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.
- Multi-step logic
Track a list of products with a target price each
“Change my price watch so it checks these five product links, each with its own target price, and names the product in the alert.”
- Any app or API
Record every reading in a Google Sheet to see the price history
“Add to my price watch: add a row to my Price history sheet with the date, product and price on every check.”
- Memory between runs
Alert on the lowest price in 90 days, not a fixed target
“Change my price watch so it alerts me when the price is the lowest it has been in the last 90 days, instead of using a fixed target.”
- Any app or API
Send the alert to a Slack channel your household or team shares
“Change my price watch so it posts drops to #deals in Slack as well as emailing me.”
- Built-in AI
Say what changed besides the price, such as stock or what's included
“Add to my price watch: when the price drops, also tell me in one line if the stock status or what's included changed.”
- Schedules
Check more often during sale weeks
“Change my price watch to check every 15 minutes from 25 to 30 November, and every 2 hours the rest of the time.”
- Trigger links
Add products by sending a link to a trigger link
“Add a trigger link to my price watch so I can add a product by sending it a link and a target price, for example from a phone shortcut.”
Questions about price drop alerts
Can ChatGPT track prices for me?
Not by itself: it checks a price only while you chat and keeps no history. Connect ClickRuntime and ChatGPT sets up an automation that checks on a schedule, keeps the readings and emails you when the price drops below your target.
Can Claude alert me when a price drops?
Yes, through ClickRuntime. Ask Claude with ClickRuntime connected; the automation runs on ClickRuntime's servers after the chat is closed.
How often can it check a price?
Every 5 minutes at most. Every few hours suits most products.
Will I get an email on every check?
No. The automation remembers whether it already told you about the current drop, so you get one email per drop.
Can it watch Amazon?
Large marketplaces often block automated page requests and offer their own product APIs. The assistant can use such an API if you have access and save its key in the ClickRuntime dashboard.
What can I add later?
More products, a price history sheet, Slack alerts or a lowest-in-90-days rule. The Extend it list on this page has prompts for each.
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 →Website change alerts
“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.”
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.