If you’re running n8n on Railway.app and wondering whether you’re on the latest version or how to update, this step-by-step guide is for you. Regularly updating n8n helps you access the latest features, security patches, and node improvements.
๐ Step 1: How to Check If Your n8n Instance Needs an Update
There are three simple ways to find out if an update is available for your n8n instance:
โ Option 1: Check the Update Notification in n8n Itself
- Log in to your n8n dashboard
- On the bottom-left corner of the sidebar, you’ll see a gift ๐ icon with the label โUpdateโ
- Click on the “Update” โ a slide-in message will appear showing the available version, release notes, and update options
This is the fastest way to know if a newer version is available inside your deployed n8n app.
โ Option 2: Check the Current Version on GitHub
- Visit the official n8n GitHub Releases
- The top-most release is the latest stable version
- Compare this with your installed version (see Option 3)
โ Option 3: Check Your Installed Version in n8n
- In your n8n dashboard, click on the
?icon or “Help” > “About n8n” - You’ll see the current version number of your instance
- If itโs older than the one on GitHub, you need to update
๐ Step 2: Deploy the New n8n Update on Railway
If an update is required, follow this easy deployment process via your Railway dashboard:
๐น Go to Railway Dashboard
- Log into Railway.app
- Select your deployed n8n project
Youโll typically see services like:
primary(core logic)worker(background processes)postgres(your database)redis(if used for queueing or caching)
๐น Redeploy the Worker Service
- Click on the
workerservice - On the top-right corner, click on the three-dot menu (โฏ)
- Choose โRedeployโ
Railway will now pull the latest container version from Docker (usually
n8nio/n8n:latestif you haven’t pinned a version).
โฑ Deployment usually takes 10 seconds to 2 minutes
๐น Repeat for the Primary Service
- Go back to your Railway dashboard
- Select the
primaryservice - Again, click the three-dot menu โ Redeploy
Wait until deployment finishes.
โ Step 3: Confirm the Update in n8n
Once deployment is complete:
- Open your n8n domain (e.g.,
https://your-n8n-app.up.railway.app) - Give it 1โ2 minutes to reload and become active
- Go to Help > About n8n and check the version
If the update was successful:
- The version number will reflect the latest release
- The โUpdateโ gift icon in the left sidebar will disappear
๐ง Pro Tips for Smooth Updates
- โ Always back up your workflows and credentials before updating
- ๐ Store secrets using Railway’s Environment Variables
- ๐ณ If using custom Docker builds, ensure your image tag is updated (
n8nio/n8n:latest) - ๐ For auto-updating, consider linking GitHub with the latest
n8nversion
๐ Final Thoughts
Keeping your n8n instance updated on Railway is easy and quick. By checking the built-in update icon or comparing versions via GitHub, youโll never miss a critical patch or feature.

