Latenode
Github

Automatically update n8n workflow automation tool on Ubuntu 24.04

This automation helps DevOps teams and system administrators running n8n (an open-source workflow automation tool) in a Docker container on an Ubuntu 24.04 server. It periodically checks for new n8n releases on the npm registry, compares the local version to the latest version, and writes the update status to a file.

A separate cron job can then read this file and execute the actual update process to ensure the n8n instance is running the most current version, improving security and access to new features. The workflow uses an HTTP request to fetch the latest version, compares it to the local version, and leverages SSH to update a status file, allowing for a seamless and automated n8n version update process.

Updated Apr 29, 2026Est. run: 7sEst. cost: $0.0004
How Latenode estimates time and cost

Latenode bills workflow runs in credits: 1 credit = 30 seconds of processing. Minimum charge per run depends on your plan. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how credits work →
Development & API

Workflow preview

What this template does

  • Monitors n8n Docker container on Ubuntu 24.04 server for new releases
  • Compares local n8n version to latest version from npm registry
  • Writes update status to a file for a separate cron job to read
  • Ensures n8n instance runs the most current version to improve security and access new features
  • Automates the process of updating n8n version to streamline DevOps and system administration tasks

How it works

1
Trigger

Scheduled Check

The workflow is triggered daily at 5am by a scheduled event.

2
Action

Fetch Latest n8n Version

The workflow fetches the latest version of n8n from the npm registry.

3
Logic

Compare Versions

The workflow compares the latest version from npm to the locally installed version of n8n.

4
Action

Write Update Status

If the local version is outdated, the workflow writes a status file indicating an update is needed.

Setup guide

1

Add GitHub credential

Add a GitHub credential in the Latenode Credentials panel. This credential will be used to fetch the latest n8n version from the GitHub releases API.

2

Configure HTTP Request node

Add an HTTP Request node to your workflow and configure it to fetch the latest n8n version from the npm registry. Set the URL to 'https://registry.npmjs.org/n8n' and the request method to 'GET'.

3

Configure Compare Versions node

Add a Compare Versions node to your workflow and configure it to compare the local n8n version (from the 'Get Local n8n version' step) with the latest version (from the 'Get the latest n8n version' step). Set the 'Comparison Operator' to 'Not Equal'.

4

Configure SSH node

Add an SSH node to your workflow and configure it to write the update status (true/false) to a file on the host system. Set the host, username, and private key credentials in the node settings.

5

Map data fields

Map the necessary data fields between the nodes in your workflow, such as the local and latest n8n versions, and the update status flag.

Requirements

Obtain GitHub personal access token with 'repo' scope to check for new n8n releases
Ensure Docker is installed on the Ubuntu 24.04 server
Set up a cron job to periodically check for n8n version updates and execute the update process
Configure SSH access to the Ubuntu 24.04 server to update the status file

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.
Contact support →

More templates

You might also like

Browse all templates →
Development & API

Automatically trigger webhooks from new Gravity Forms entries

This automation template allows users to trigger a custom webhook URL whenever a new entry is submitted through a Gravity Forms integration. The automation is designed for developers, API users, and infrastructure teams who need to build custom integrations and workflows that respond to data from Gravity Forms. It involves connecting Gravity Forms to a webhook endpoint, which could then forward the form data to another system or service for further processing. This enables users to build custom backend logic and integrations around their Gravity Forms data without having to manually monitor the form or build a custom integration from scratch.

26s$0.0703
Development & API

Automatically create Knack records from external data webhooks

This automation allows users to automatically receive data from an external source via a webhook and use that information to create a new record in a specified Knack application. The automation is designed for developers, IT professionals, and others who need to integrate external data sources with their internal applications. It involves setting up a webhook to receive data from an external source, processing that data, and then creating a new record in a Knack application based on the received information. The automation helps streamline data integration and reduces the need for manual data entry, improving efficiency and productivity.

26s$0.0703
Development & API

Automatically generate OpsGenie alerts from incoming webhooks

This automation template monitors incoming webhooks for specific events, such as infrastructure changes or application errors, and automatically generates corresponding alerts in the OpsGenie incident management platform. This allows the relevant development, API, and infrastructure teams to be notified promptly so they can investigate and resolve issues. The automation streamlines the incident response process, improving operational efficiency and reducing the time to resolution for critical events.

26s$0.0703