Guides

Connect Render to Uptimy Cloud

Paste a Render API key, pick your services, and get a monitor for each, incidents for failed deploys and crashes, and automatic restarts. About five minutes.

Uptimy Cloud or Uptimy Agent?

This guide connects Render to Uptimy Cloud, which checks your services from outside Render and can restart them. To check private services and databases from inside your Render workspace, use the open-source Uptimy Agent instead, or next to it: see Deploy Uptimy Agent on Render.

Overview

Uptimy's Render integration reads your Render services with an API key and sets up three things:

  • Monitors: an HTTP check for each web service and static site, at its custom domain or onrender.com address, from several regions. Every plan, within its monitor limits.
  • Deploy and crash events: a failed deploy or a service that stops answering opens an incident, including for background workers and cron jobs, which have no address to check. Needs a Render workspace on Pro or above.
  • Self-healing: a workflow that restarts a service when its incident opens, with limits that stop a flapping service from restarting in a loop. Growth and above.

1. Create a Render API key

In Render, open Account Settings → API Keys and create a key. A Render API key can see every Render workspace you belong to. Uptimy uses it to list your services, and to restart the ones you import from a self-healing workflow. It's encrypted at rest and never shown again.

2. Import your services

New to Uptimy? Create an account and choose Import from Render during setup. When the key sees one Render workspace, the Uptimy workspace is named after it.

In an existing workspace:

  1. Open Settings → Integrations, choose Render and paste the key.
  2. Click Import monitors on the Render card.
  3. Untick the services you don't want, adjust each health path and expected status, and import.

Services without a public address, such as background workers, cron jobs and private services, are added without a monitor. They still get deploy and crash incidents, and can still be restarted. Imported monitors count toward your plan's limits.

3. Turn on deploy and crash events

On the Render card in Settings → Integrations, click Webhook URL and copy it. The URL contains a secret, so treat it like a password. Then, in Render:

  1. Open Integrations → Webhooks in your workspace and click Create Webhook.
  2. Paste the URL.
  3. Pick the events deploy_ended, server_failed and server_available, and create it.

From then on, for every service you imported:

  • A failed deploy opens an incident. The previous deploy keeps serving, so it's a notch below a crash.
  • A service that fails (Render's server_failed) opens a high-severity incident. Three in ten minutes escalate it to critical.
  • A deploy that goes live, or the service becoming available again, resolves it.

Events for services you didn't import are ignored.

Render plans

Render only allows webhooks on Pro workspaces and above, and only workspace admins can create them. On other plans, monitors and restarts work without events. Add the webhook whenever the workspace moves to Pro.

4. Restart services automatically

After the import, Create self-healing workflow builds a workflow with one branch per imported service: when that service's monitor opens an incident, the Render self-heal step restarts it. Render restarts are zero-downtime: a new instance starts, then traffic moves over.

The step comes with guardrails:

  • A resolved incident never triggers a restart.
  • A cooldown between restarts of the same service, 10 minutes by default.
  • At most 3 restarts per incident by default. If those didn't fix it, a fourth won't.
  • Only services you imported can be restarted, whatever else the key can see.

Every restart, and every one skipped with its reason, is in the workflow's run details. Add a message step after it so a person hears about restarts too. See Workflows.

Plans

Importing and monitoring work on every plan. The Render self-heal step comes with Growth and above.

Private services and databases

Uptimy checks from outside Render, so private services and Render Postgres and Key Value have no address it can reach. For those, run the open-source Uptimy Agent: its Settings → Import from Render takes the same API key, and when the agent runs on Render in the same workspace and region it checks services over Render's private network. Connected to Uptimy Cloud, its monitors show up next to the others.

Troubleshooting

  • No incidents for failed deploys or crashes: check that the webhook is in the Render workspace the service belongs to, with the three events picked, and that the service was imported. A Pro workspace allows one webhook, so it may already be used for something else.
  • A service is missing from the self-heal step: only imported services are listed. Run Import monitors again to add it.
  • A restart failed: the run details show Render's answer. Cron jobs can't be restarted, and a revoked API key fails every call. Connect a new key under Settings → Integrations.

Next steps