Every 5 minutes

Know the moment your website goes down

Your team hears in Slack when the site stops responding or slows down, and again when it's back.

Runs: Every 5 minutes
Apps: Slack
AI: Not needed
Access: chat:write

Send this to your assistant

Create a ClickRuntime automation: every 5 minutes, check example.com and example.com/pricing. Post to #ops if either is down or takes more than 3 seconds, and again when it recovers.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A site goes down at 3 a.m. after a hosting change. The first notice is a customer's email on Monday morning, or a sales rep who found the pricing page returning an error. The same blind spots apply to a TLS certificate that expires without anyone renewing it, which shows visitors a full-page browser warning, and to a link on a landing page that quietly turns into a 404 after a redesign. Each costs conversions, search ranking and trust before anyone sees it.

Every five minutes, ClickRuntime requests each of your URLs, reads certificate expiry dates and can crawl your sitemap for broken links. It compares each result with the last status it recorded and posts to Slack only when something changes: down, recovered, certificate within its warning window, or a newly broken link.

Small agencies, ecommerce owners and freelancers who look after several sites and do not want another monitoring subscription use it.

What you get out of it

Downtime is noticed in minutes
A five-minute check shortens the gap between a site failing and a person knowing about it, which for a store can be the difference between losing a few orders and losing a weekend of sales.
Certificate expiries stop being surprises
A warning weeks ahead gives time to renew without panic. An expired certificate blocks visitors with a security warning, and most of them will not click through to continue. The renewal becomes a calm task on a calendar, not an emergency on a weekend.
Alerts are not repeated every five minutes
Only changes are posted, so one outage produces a down message and a recovered message. The channel stays quiet enough that a new alert is read and taken seriously. People also trust the channel more when it never cries wolf.
Broken links are fixed before search engines notice
Dead internal links hurt user trust and crawl efficiency. Listing them regularly lets a content editor repair redirects, so rankings and paid landing pages are not damaged for months. Fixing them early also keeps visitors from landing on dead ends.
Agencies can show clients proof
A channel history of down and recovered times lets an agency answer "was the site down on Tuesday?" with facts, and it supports honest conversations about hosting quality. That record also protects the agency when a client blames a plugin update.

How it works

What happens, step by step

Every five minutes ClickRuntime opens each page of your website on your list.
It treats a page as down if it returns an error or takes longer than a few seconds to load.
It compares the result with the last check, so you only hear about changes, not every check.
When a page goes down or comes back, a message goes to your Slack channel with the page address and what was seen.

Before it runs live

Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)

What you get

RunsEvery 5 minutes

Know the moment your website goes downtoday, 9:00Succeeded

Slack · #ops🔴 Down or slow: https://example.com/pricing (HTTP 200 in 4.8s)

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Google Sheets
Combine it with other Slack steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

website_uptime_ssl_and_broken_link_checks.pyexample

from clickruntime import on_trigger, state, http, notify

URLS = ["https://example.com", "https://example.com/pricing"]
SLOW_SECONDS = 3

@on_trigger
def run(event):
    status = state.get("status") or {}
    changes = []
    for url in URLS:
        try:
            resp = http.get(url, timeout=10)
            secs = resp.elapsed.total_seconds()
            ok = resp.status_code < 400 and secs <= SLOW_SECONDS
            detail = f"HTTP {resp.status_code} in {secs:.1f}s"
        except Exception as e:
            ok, detail = False, type(e).__name__
        if status.get(url, True) != ok:
            changes.append(f"{':white_check_mark: Recovered' if ok else ':red_circle: Down or slow'}: {url} ({detail})")
        status[url] = ok
    for line in changes:
        notify.slack(line, channel="#ops")
    state.set("status", status)
    return {"changes": len(changes)}

FAQ

Common questions

How does it avoid false alarms from a single failed request?

It compares the result with the previous status, and a check can require two failures in a row before reporting an outage. That avoids waking people over a one-off network blip between the checker and your server.

How far ahead does the certificate warning come?

You set the window, commonly 14 or 30 days before expiry. When the date falls inside it, the alert is posted once and then repeated only if the certificate is still unrenewed at your chosen follow-up point.

Can it check pages behind a login?

It checks anything reachable by a plain request, and can send a header such as a token stored as a secret. Pages that need a full interactive login or JavaScript sign-in flow cannot be tested this way.

What permissions does it need?

chat:write. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (every 5 minutes). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Daily