Automation · Operations and reporting
Check on WhatsApp whether your Render site is down and what the logs say
Ask on WhatsApp whether your Render site is down: an AI agent checks the service, the latest deploy, the logs and the metrics.
How do I know whether my Render site is down without opening the dashboard?
You write to your Met "is the site down?". The Met lists your Render workspaces, finds the site's service and brings its details. It checks the latest deploy to see whether it finished or failed, reads the error logs from the last hour and checks the CPU, memory and HTTP request metrics. It replies with what it found: whether the deploy failed, which error shows up in the logs and what the traffic looks like. Everything is read-only: the Met does not redeploy or change anything in this procedure.
What starts it
When someone asks for it
It starts when someone on the team asks the Met on WhatsApp whether the site is down or why it is slow. Each check runs on request; the Met does not watch the site on its own.
A manual task: someone on the team runs it with a button, or asks the Met for it in chat.
Who runs it
Internal Met that checks your Render infrastructure
This is not a named, seeded Met. It is an internal Met with Render connected, for the owner or the agency that maintains the site: its work ends when it tells you what it found in the service, the deploy, the logs and the metrics.
Channels: WhatsApp
What you need connected
- Render Automate and collaborate
5 steps · 7 tools
The procedure, step by step
Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.
- 1
Find the workspace
The Met lists the Render workspaces the API key can access and uses the one that belongs to your business in the next queries.
- 2
Find the site's service
The Met lists the services and brings the details of the one that serves your site. If you have several, it uses the name you gave it in its instructions so it does not check the wrong one.
- 3
Check the latest deploy
The Met brings the service's deploy history and the details of the most recent one, to see whether it finished or failed and when it happened.
- 4
Read the error logs
The Met lists the service's logs filtered by error level and by the last hour, and takes the messages that repeat to tell you what is failing.
- 5
Look at the metrics and reply
The Met brings the service's CPU, memory and HTTP requests for the last hour and replies with a summary of what it saw in the deploy, the logs and the metrics.
Before you start
What you need ready
The Met solves none of these for you. If one is missing, the automation stops there.
-
Render connected with an API key
In the Render dashboard, open Account Settings → API Keys and create a key. Then, in Met, open Connections → Render → Connect and paste the key.
-
An internal Met on WhatsApp
Assign the connector to a Met that only serves the team, not the one that talks to customers, because the same connection brings actions that deploy and create resources, even though they start turned off.
-
The service name in the instructions
Write in the Met's instructions which service is your site and which workspace it is in, so it always checks the right one.
The limits
What this automation does NOT solve
Better said here than discovered halfway through the rollout.
-
It does not fix the outage. The Met tells you what it found; redeploying or fixing the code is another action in the listing, which this procedure does not use.
-
It does not alert you on its own when the site goes down. The check starts when someone asks the Met; for alerts, Render has its own notifications.
-
It does not see failures outside Render, such as an expired domain at another provider. The logs and metrics only show what happens inside your service.
-
It does not bring metrics older than 30 days, and response times need a Pro workspace or higher on Render.
FAQ
Questions about this automation
The Render listing has the deploy action, but this procedure does not use it and it starts turned off. If you want the Met to redeploy, the admin turns it on in Connections and you ask for it in another instruction.
This procedure does not ask for them. Render tries not to expose sensitive data such as connection strings, but says it does not guarantee it, so it is best to use a Met that only serves the team.
Yes. A static site is also a service on Render, with its deploy history. HTTP traffic metrics are for web services.
Keep going
Other automations built on the same tools
Operations and reporting
Turn off on WhatsApp the feature flag that breaks the checkout in LaunchDarkly
How do I quickly turn off a feature flag that broke the checkout without opening LaunchDarkly?
- Starts:
- when someone asks for it
- Steps:
- 5, with 7 real tools
- Needs:
- LaunchDarkly
Operations and reporting
Build a department's higher education report without opening SNIES
How do I pull SNIES enrollment and program figures without going into the portal?
- Starts:
- when the customer writes
- Steps:
- 5, with 5 real tools
- Needs:
- SNIES
Operations and reporting
Build your team's org chart in Lucid on WhatsApp and share it
How do I build my business's org chart without sitting down to draw it?
- Starts:
- when someone asks for it
- Steps:
- 6, with 6 real tools
- Needs:
- Lucid
Operations and reporting
Tell customers on your status page that the store is down, asking on WhatsApp with Better Stack
How do I tell my customers my online store is down without opening Better Stack?
- Starts:
- when someone asks for it
- Steps:
- 6, with 6 real tools
- Needs:
- Better Stack
Want this automation running on your own data?
We will show it to you with your accounts connected, not with a canned demo.