Get told when your site goes down, set up from your AI assistant
Ask your assistant to watch your site or API. ClickRuntime requests it on a schedule, checks the status code, response time and a word that should be on the page, and alerts you once when it's down and once when it's back.
- When
- Every 5 minutes
- Uses
- app.example.com, Slack #ops
- 09:35✓ App uptime check · SucceededLast run09:35 · 200 in 182 ms
Can ChatGPT or Claude tell me when my website is down?
Not on their own: they only check when you ask, and they can't message you at night. With ClickRuntime connected, your assistant sets up a check that requests your site every 5 minutes or slower, counts failures in a row and alerts you in Slack or by email, then again when it recovers.
Why the assistant can’t do this on its own
- Downtime happens when nobody is chatting. A check has to run on a timer, outside the conversation.
- One failed request is often a blip. Alerting after two or three failures in a row needs a count kept between checks, which a chat doesn't have.
- “It's back up” needs to know it was down. The automation's state holds that.
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 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.” 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 keysAlerts to Slack use the workspace notifications Slack: the assistant gives you a link to connect it once in the ClickRuntime dashboard and asks for the channel. Email alerts need nothing. If the endpoint needs a token, save it as a secret in the ClickRuntime dashboard.
- Step 5Test itThe assistant runs it once and shows the status and response time. To see an alert without real downtime, it can run a test against a URL that returns an error, then switch back.
- 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 status code and time, for example “200 in 182 ms”. Failed checks show the reason. State holds the failure count and when the outage started. The run history doubles as a simple uptime log.
“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.”
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.
- Status, time and body are checked with plain code, so no AI tokens are used.
- The failure counter in state stops one-off blips from alerting anyone.
- One alert per outage and one when it recovers, because the outage start is kept in state.
- Daily counters of good and failed checks let a weekly report work out uptime later.
A schedule, not a trigger link
Use a schedule, every 5 minutes for production sites. That is the shortest interval, so this suits knowing within about 10 minutes rather than second-by-second paging.
Each check is one run: every 5 minutes is about 8,640 runs a month, so pick a plan that covers it, or check every 30 minutes for a side project.
Limits
- The shortest interval is every 5 minutes, and checks come from ClickRuntime's servers in one region.
- Only HTTPS on port 443. Ping, other TCP ports and plain HTTP aren't available.
- This is a check you own and can extend, not a status page or on-call rota. For paging with escalation, have the automation call your incident tool's API.
Troubleshooting
It alerts but the site looks fine to me.
Read the failed run's reason. A response slower than the timeout, or a firewall that blocks cloud addresses, are common. Ask your assistant to raise the timeout, or allow the request on your side.
Alerts don't reach Slack.
The run fails with a notify error when the notifications Slack isn't connected or no channel was set. Connect it in the ClickRuntime dashboard and invite the app to the channel.
Can it check several URLs?
Yes, one automation can loop over a list and keep a counter for each. Ask your assistant to add them.
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
Check your site, API and checkout page in one automation
“Change my uptime check so it also checks https://api.example.com/health and https://example.com/checkout, and names which one failed.”
- Memory between runs
A weekly uptime report from the daily counters
“Add to my uptime check: every Monday at 9, email me last week's uptime percentage per day.”
- Any app or API
Open an incident in Linear when the site stays down
“Add to my uptime check: if it's still down after 15 minutes, create an urgent issue in Linear with the failure details.”
- Any app or API
Text the on-call phone through Twilio
“Change my uptime check so it also sends an SMS through Twilio to our on-call number when the site goes down.”
- Built-in AI
Explain the error page in plain words in the alert
“Change my uptime check so when it gets an error page, it adds a one-line plain explanation of the error to the alert.”
- Trigger links
Let deploys mute the alerts for a few minutes
“Add a trigger link to my uptime check that our deploy script calls to mute alerts for 10 minutes during a deploy.”
- Schedules
Check SSL expiry once a day alongside uptime
“Add to my uptime check: once a day at 8, check the SSL certificate and alert #ops if it expires within 14 days.”
Questions about uptime checks
Can ChatGPT monitor my website's uptime?
Not on its own, because it acts only while you chat. With ClickRuntime connected, ChatGPT sets up a check that runs every 5 minutes or slower and alerts you in Slack or by email.
Can Claude check if my site is down?
Yes, through ClickRuntime. Claude writes the check and turns it on; it keeps running on ClickRuntime's servers after the chat is closed.
How quickly will I know?
With checks every 5 minutes and an alert after two failures, usually within about 10 minutes.
Does it replace a dedicated uptime service?
For a few sites and simple rules, often yes. Dedicated services check from many regions and run status pages; ClickRuntime is for checks with your own logic, such as reading a page's content or opening a ticket.
How many runs does it use?
One per check: about 8,640 a month at every 5 minutes, or 1,440 at every 30 minutes.
What can I add later?
More URLs, an incident ticket, SMS, a weekly uptime report or an SSL check. See the Extend it list.
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 →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 →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.