Skip to content
ClickRuntime

Automate Railway

On Railway the things worth watching are deployments and services: a deploy that fails, a service that crashes, a volume filling up, or a bill creeping higher. ClickRuntime reacts to Railway's own events the moment they fire and runs scheduled jobs against your projects, such as a nightly restart or a Friday deploy log. Explain the job to your AI assistant in plain words, confirm the steps it lays out, and it carries on without you watching the dashboard.

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

Try asking

Create a ClickRuntime automation: give me a webhook link for my Railway project and email me whenever a deployment there fails or crashes, with the service name and a link.

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

Ideas

What you can automate in Railway

Instant notice of crashed or failed deploys and resource alerts, a weekly look at estimated spend and deployment history, and a service that restarts itself every night. These are ready-made starting points. Anything else you can describe works too.
The moment it happens

Get an email when a Railway deploy fails or crashes

As soon as a deployment in your project fails or crashes, an email tells you which service and what happened.

See how it works
The moment it happens

Get Slack alerts for full volumes and high CPU or memory

When Railway flags a volume near capacity or a CPU or memory alert, the details are posted to your ops channel.

See how it works
Weekly

See your estimated Railway spend each week

Every Monday you get an email with each project's estimated usage so far this month.

See how it works
Daily

Restart a Railway service every night

Your service gets a fresh restart at a quiet hour, and you only hear about it if the restart fails.

See how it works
Weekly

Get a Friday log of this week's deployments

At the end of the week you see every deployment in the project with its status, plus a count of how many succeeded and failed.

See how it works Your own logic

Any other automation you can describe in words

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

See how to build your own

Build your own

Build any Railway automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Railway 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 Railway services and tell me if any deployment has crashed.

When a Railway deployment succeeds, post the service and commit message to Slack.

Every day, check Railway project usage and cost, log it in Google Sheets, and send me a Telegram alert if the month is on track to exceed my budget.

Beyond chat

Have Railway work when you're not in the chat

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

Railway connects with a token you create in your Railway account. A workspace token is the best fit for automations because it covers that workspace's projects and nothing else.

Railway

Developer / Hosting

  1. In Railway, open Account Settings and go to Tokens.
  2. Choose Create Token and pick the workspace the automations should use. Leave the workspace empty only if you need an account-wide token.
  3. For a single project, you can instead create a token under that project's Settings, then Tokens.
  4. Copy the token. Account and workspace tokens are sent as Authorization: Bearer <token>.
  5. In the ClickRuntime dashboard, open Connections & secrets and save the token as a secret for Railway.

Good to know

Railway limits that affect automations

  • Railway's API is GraphQL. A bad or expired token still returns HTTP 200, with the problem in an errors array, so automations check that array rather than the status code.
  • Crash, failed deploy and resource alerts arrive through webhooks that you add per project, so each project you want covered needs its own webhook.
  • Queries about your own user only work with an account token. Workspace and project tokens are limited to what they were created for.
  • Older Railway docs call workspace tokens team tokens. They are the same thing.

FAQ

Questions about automating Railway

What can ClickRuntime do in my Railway projects?
Whatever the token you saved allows. With a workspace token it can read projects, services and deployments and restart a deployment. A project token keeps it to one project.
Are deploy failures reported in real time?
Yes. Railway sends a webhook when a deployment changes status, and ClickRuntime forwards only the failed and crashed ones. You add the webhook link in each project's settings.
Which token should I use?
A workspace token for most automations, since it is scoped to one workspace. Use a project token when an automation should only ever touch one project, and an account token only if you need account-level details.
Can it restart a service for me?
Yes. A scheduled automation can find the latest successful deployment of a service and restart it, then email you if the restart did not go through.
Do Railway automations need AI?
No. Alerts, restarts and weekly logs are plain status checks. If you want a written explanation of a failure, the AI that is part of every ClickRuntime plan can add one without an AI key from you.
Is this a Railway connector for ChatGPT or Claude?
Not for chatting with Railway data. A chat connector lets your assistant read and change Railway 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 Railway event.

Related pages

Keep exploring

Tell your assistant what Railway should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude