Skip to content
ClickRuntime

Automate Render

Render runs your web services, workers and Postgres databases, and the moments that need attention are a failed build, a service going down, or a free database about to expire. Automations watch deploys and service health, send a weekly tally of deploys per service, and warn you a week before a free database runs out. Describe the alert to your assistant, approve the steps it shows you, and it keeps checking without you.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every 5 minutes check my Render services and post to #deploys in Slack when a deploy fails, with the service name, commit message and a link to the deploy.

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

Ideas

What you can automate in Render

Failed deploys posted to Slack, down-service alerts, a weekly deploy scorecard, and early warning before a free Postgres database expires. These are ready-made starting points. Anything else you can describe works too.
Every 5 minutes

Get failed Render deploys posted to Slack

Within 5 minutes of a build or update failing, the service and deploy show up in your Slack channel.

See how it works
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.

See how it works
Weekly

Get a weekly count of Render deploys

Each Monday you see how many deploys succeeded and failed for each service over the past week.

See how it works
Daily

Get warned before a free Render database expires

A week before a free Postgres database's expiry date, you get one email naming it.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Render, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Render automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Render should do in your own words, with your conditions, other apps or an AI step, and 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.

For example, ask your assistant

Every 10 minutes, check my Render services and alert me if any service is suspended or its latest deploy failed.

When a Render deploy goes live, post the service name and commit to Slack.

Every hour, check my Render services' status and my health URL's response time, log both in Google Sheets, and alert me on Telegram if anything is down.

Beyond chat

Have Render work when you're not in the chat

Connecting Render to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Render

Render connects with an API key you create in your Render account settings. The key is shown only once, so copy it before closing the page.

Render

Developer / Hosting

  1. In the Render dashboard, open Account Settings and go to API Keys.
  2. Create an API key and copy it right away; Render won't show it again.
  3. In the ClickRuntime dashboard, open Connections & secrets and save the key as a secret for Render.

Good to know

Render limits that affect automations

  • A Render API key reaches every workspace you belong to and can't be narrowed to one service or to read-only.
  • You can revoke a key from the Render dashboard at any time, which stops all automations using it.
  • Render webhooks need a Pro plan or higher; on other plans the deploy alert checks every 5 minutes instead.
  • Only free-tier Postgres databases have an expiry date, so the expiry warning skips paid databases.

FAQ

Questions about automating Render

What can ClickRuntime access on Render?
The key has full access to all your workspaces, because Render keys aren't scoped. The ready automations only read services, deploys and databases; they don't redeploy, scale or delete anything.
How soon will I hear about a failed deploy?
On Pro plans and up, a webhook can deliver it as it happens. On any plan, polling every 5 minutes catches deploys whose build or update failed.
Can I keep the key away from some workspaces?
Not with Render's API keys. If that matters, create the key from a Render user who belongs only to the workspaces you want watched.
Why warn me about a database expiring?
Free Render Postgres databases have an expiry date. The daily check emails you once per database when it's within 7 days, giving you time to upgrade or export the data.
Is AI part of these Render automations?
No, they compare statuses and dates. Should you want a summary written for you, every ClickRuntime plan includes AI, so you don't need to bring a key.
Is this a Render connector for ChatGPT or Claude?
Not for chatting with Render data. A chat connector lets your assistant read and change Render while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Render event.

Related pages

Keep exploring

Tell your assistant what Render should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude