The moment it happens

Get an email when a Render service goes down

When a service fails or turns unhealthy, an email tells you which one so you can look straight away.

Runs: The moment it happens
Apps: Render
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: email me when any of my Render services fails or becomes unhealthy, with the service name and the time it happened.

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 web service on Render stops responding because it ran out of memory, a dependency timed out or a health check began to fail. Customers see error pages, and the person who finds out first is often the one writing to support, not the team who could fix it. Each minute of downtime costs orders, signups or trust.

When Render emits an event that a service has become unhealthy or is down, ClickRuntime receives it immediately, looks up the service name so the message is readable, and notifies you with what happened and a link to the service. You hear about it from the platform itself, not from an unhappy user.

It fits any small team without a dedicated monitoring tool that still needs to know quickly when production is in trouble.

What you get out of it

Downtime is cut short
Starting the response the minute a service goes unhealthy shortens the outage. Every minute saved is revenue kept and customers who never saw an error. Faster recovery protects both sales and reputation.
You hear before your customers do
Learning about a problem from your own alert rather than from a support ticket protects your reputation. Customers who find the issue already acknowledged trust you more. Support can then answer calmly.
The right service is named
In a project with several services, a bare event is not much use. Looking up the name turns it into a clear message that tells whoever is on call where to look.
No separate monitoring bill
Render already knows when a service is unhealthy. Delivering that to your inbox or chat means basic uptime awareness without paying for and configuring another tool. Small teams get uptime awareness without another subscription.
On-call duties become shareable
A message in a channel can be picked up by whoever is available. That makes it easier for a small team to share responsibility fairly across days and evenings. Nobody has to carry the pager alone.

How it works

What happens, step by step

When a Render service fails or turns unhealthy, Render tells ClickRuntime straight away.
ClickRuntime looks up the service's name.
You get an email naming the service, what happened and when.

Before it runs live

Connect Render
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Get an email when a Render service goes downjust nowSucceeded

Email · Render serviceRender service api-server: server failed Time: 2026-10-19T04:12:08Z

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

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Render 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.

get_alerted_when_a_service_goes_unhealthy.pyexample

from clickruntime import on_event, credentials, http, notify

RENDER = "https://api.render.com/v1"

def render(path, **params):
    resp = http.get(f"{RENDER}{path}", params=params, headers={"Authorization": f"Bearer {credentials.secret('RENDER_API_KEY')}"})
    resp.raise_for_status()
    return resp.json()

@on_event
def handle(event):
    body = event.json
    if body.get("type") not in ("server_failed", "server_unhealthy"):
        return {"skipped": body.get("type")}
    service_id = body["data"]["serviceId"]
    name = render(f"/services/{service_id}")["name"]
    notify.email_me(f"Render service {name}: {body['type'].replace('_', ' ')}", f"Service: {name}\nTime: {body['timestamp']}")
    return {"service": service_id}

FAQ

Common questions

How does Render know a service is unhealthy?

Render checks the health check path you configure for a web service and also notices crashes and restarts. When those checks fail, it sends a notification event. Without a health check path, it relies mostly on the process staying up.

How is this different from Render's own email notifications?

Render can email account owners about some events, but those go to fixed addresses and formats. This sends the alert where your team actually works, such as Slack or SMS, and adds the readable service name and link.

Does it alert when the service recovers?

It can. Render also sends an event when a service becomes healthy again, and a recovery message can be added. Many teams like seeing the all-clear in the same thread, so they know when an incident is over.

What permissions does it need?

read. 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 for each event the app sends.

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.

Every 5 minutes