Compare Your Instance Version with Latest Release - n8n Workflow

• System administrators managing self-hosted n8n instances.


• Developers who need to ensure software consistency across environments.


• Users looking for advanced examples of using the n8n API and HTTP Request n8n node.


• Anyone relying on up-to-date n8n templates for critical operations.

Maintaining an up-to-date n8n instance is crucial for security and access to new features. This specialized n8n workflow template solves the problem of manually checking and comparing versions. It fetches the latest release information directly from the official n8n documentation and then uses the n8n API to pull your instance's running version. The core logic of this n8n workflow uses an If n8n node to perform the comparison, alerting you instantly if your version is outdated. This is an essential devops monitoring tool built entirely within n8n.

This n8n workflow executes in several steps:

1. Fetching the Latest Version: The process starts with an HTTP Request n8n node (Get Most Recent n8n version) that scrapes the n8n release notes page to find the most recently announced version.


2. Data Extraction: The HTML n8n node (Extract Version) precisely isolates the version string using a CSS selector targeting the h2 elements containing 'n8n@'.


3. Data Cleanup: A Code n8n node (Clean Value) standardizes the data by removing unnecessary prefixes (like 'n8n@') and suffixes, ensuring a clean, comparable version number.


4. Retrieving Local Version: Another HTTP Request n8n node (Get your n8n version) uses your configured n8n API credentials to call the local /rest/settings endpoint. This retrieves metadata about your running n8n instance, including the versionCli field.


5. Comparison: The final If n8n node (Test your version) compares the local versionCli against the cleaned official latest version. This comparison determines if your n8n node setup is running the most current release.

To install this n8n workflow template, follow these steps:

1. Import the n8n workflow: Copy the provided JSON data and paste it into your n8n instance using the 'Import from JSON' option.


2. Set up n8n API Credentials: This is essential for the n8n node that reads your instance settings.

1. Configure Credentials in the n8n workflow: Attach the newly created n8n API credential to the Get your n8n version HTTP Request n8n node. This ensures the n8n workflow can communicate with itself.


2. Replace Placeholder: Update the URL in the Get your n8n version n8n node (e.g., https://yourn8nurl.app.n8n.cloud/rest/settings) with the actual URL of your n8n instance.


3. Execution: Run the n8n workflow manually or configure a schedule n8n trigger to run it periodically.

HTTP Request (Get Most Recent n8n version):
Function: Fetches the HTML content from the official n8n release notes page to find the latest version number.
Key Configuration: URL is set to https://docs.n8n.io/release-notes/.
HTML (Extract Version):
Function: Parses the returned HTML to extract the specific text containing the version.
Key Configuration: Uses the CSS Selector h2:contains("n8n@").
Code (Clean Value):
Function: Cleans up the extracted version string, removing prefixes like 'n8n@' to ensure a pure version number for comparison. This is a crucial step in this n8n workflow template.
Key Configuration: Contains custom JavaScript logic for string manipulation.
HTTP Request (Get your n8n version):
Function: Authenticated API call to the running n8n instance's settings endpoint to retrieve the currently installed version (versionCli).
Key Configuration: Uses the n8n API Credential type and targets the local /rest/settings path.
If (Test your version):
Function: Compares the two extracted version values (local vs. official) to check for equality.
* Key Configuration: Compares the versionCli output from the local API call against the cleaned output of the latest version.