Skip to content
ClickRuntime

Automate Heroku

On Heroku the things that go wrong quietly are crashed dynos, failed releases, and apps and add-ons nobody remembers paying for. Automations alert you when a dyno crashes or a release fails, list every app with its dyno formation each week, and total up add-on costs each month. Ask your AI assistant for the check you want, read through what it's going to do, and it keeps watching your apps from then on.

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

Try asking

Create a ClickRuntime automation: email me when any dyno of my Heroku app 'shop-api-prod' crashes, with the dyno name and time. Only send one email per crash.

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

Ideas

What you can automate in Heroku

Crash and failed-release alerts for the whole team, a weekly inventory of apps and dynos, and a monthly add-on bill with anything new flagged. These are ready-made starting points. Anything else you can describe works too.
The moment it happens

Get alerted when a Heroku dyno crashes

When any dyno of your app enters a crashed state, you get one email about it.

See how it works
Every 5 minutes

Tell the team in Slack when a Heroku release fails

A failed release is posted to your team channel, so it isn't only the person who pushed who knows.

See how it works
Weekly

Get a weekly list of your Heroku apps and dynos

Each Monday you see every app with its dyno types and counts, which makes forgotten apps easy to spot.

See how it works
Monthly

Get a monthly report of Heroku add-on costs

On the 1st you receive every add-on across your apps with its plan and monthly price, with new ones highlighted.

See how it works Your own logic

Any other automation you can describe in words

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

See how to build your own

Build your own

Build any Heroku automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Heroku 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 Heroku apps for crashed dynos and restart them, then tell me which ones restarted.

When a Heroku release is created on production, post the app, version and who deployed to Slack.

Every morning, take Heroku app errors and Sentry issues from the last day, have AI group them by likely cause, and post the summary to our #eng Slack channel.

Beyond chat

Have Heroku work when you're not in the chat

Connecting Heroku 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 Heroku

Heroku connects with a long-lived authorization token you create yourself, either from the Heroku CLI or in your account settings. You can limit it to read access.

Heroku

Developer / Hosting (PaaS)

  1. Run heroku authorizations:create -d "ClickRuntime" and copy the Token value, or create one in your Heroku account settings under Applications, Authorizations.
  2. Use the read scope for alerts and reports; use write only if the automation should create a webhook on your app for instant dyno alerts.
  3. Avoid heroku auth:token for this, since that token expires.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the token as a secret for Heroku.

Good to know

Heroku limits that affect automations

  • Accounts that sign in through federated SSO can't create authorizations. Heroku suggests a separate non-SSO user in your org for this.
  • Authorizations can be scoped to read, write or global; a read-only token can watch apps but not change them.
  • Instant dyno and release alerts need a Heroku webhook on the app, which takes a write-scoped token or a one-time CLI step. Otherwise the automation checks every 5 minutes.
  • Add-ons on contract pricing have no list price in the API, so reports show them as "contract" instead of a figure.

FAQ

Questions about automating Heroku

What can ClickRuntime see in my Heroku account?
Whatever your authorization's scope allows across the apps your user can access: apps, dynos and their states, releases and add-ons. With a `read` token it can't restart, scale or deploy anything.
Will I hear about a crash straight away?
If a webhook is set up on the app, yes, the dyno event arrives as it happens. Without one, the automation lists dynos every 5 minutes. Either way you get one alert per incident, not one per check.
I log in to Heroku through SSO. Can I still connect?
Federated SSO users can't create authorizations, so create the token from a separate Heroku user in your org that doesn't sign in through your identity provider.
How is the add-on cost report worked out?
It lists the add-ons on each app with plan name and billed monthly price, adds them up, and compares the list with last month's to point out new ones.
Do these alerts use AI?
No, they are straightforward status checks. If you want an error explained in plain language, the AI that ships with every ClickRuntime plan can add that, and no AI key of yours is needed.
Is this a Heroku connector for ChatGPT or Claude?
Not for chatting with Heroku data. A chat connector lets your assistant read and change Heroku 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 Heroku event.

Related pages

Keep exploring

Tell your assistant what Heroku should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude