V1 Upgrade Expression Audit Tool - n8n Workflow

A helper n8n workflow for system administrators and developers:
n8n users who recently upgraded their instance to n8n v1.
Automation specialists debugging legacy n8n workflow logic after a major version change.
Developers seeking to audit their existing n8n templates for hidden compatibility issues.
Anyone managing complex n8n infrastructure needing quick verification of core flow functionality.

The transition to n8n v1 introduced breaking changes, particularly concerning certain date and arithmetic expression extensions (like beginningOf or minus). This powerful n8n workflow acts as a critical post-upgrade diagnostic tool. It solves the problem of manually sifting through potentially hundreds of n8n nodes within multiple complex n8n templates. By automating this review, the user gains a quick, actionable list of every parameter across every active n8n workflow that uses an expression potentially impacted by the update, ensuring they can verify continued correct operation immediately after the n8n upgrade. This is a crucial n8n template for maintaining stability.

This diagnostic n8n workflow operates by pulling the source code of all active flows and applying custom JavaScript logic to detect deprecated expression syntax.

1. The process is initiated using a Manual n8n trigger, labeled 'When clicking "Execute Workflow"', starting the analysis n8n workflow execution on demand.


2. The workflow immediately uses the core n8n node (labeled 'n8n') to retrieve the full JSON structure of all currently active n8n templates running on the instance via the n8n API.


3. A highly optimized Code n8n node executes custom JavaScript. This code defines a list of affected expression extensions (beginningOf, endOfMonth, minus, plus) specific to the n8n v1 changes.


4. The Code n8n node recursively searches through the parameters of every single n8n node within every retrieved n8n workflow JSON structure.


5. If an affected expression is detected in any parameter value, the Code n8n node generates an output item detailing the workflowName, the nodeName, and the specific parameterName.


6. The final output of this n8n template is a consolidated list identifying every single location requiring manual review and potential modification following the n8n v1 upgrade.

1. Import the n8n Workflow: Copy the provided JSON data and import it into your n8n instance via the 'Workflows' screen using the 'New' -> 'Import from JSON' option.


2. Set n8n Credentials: You must configure the 'n8n' n8n node with valid API credentials that have access to retrieve workflow definitions from your instance. Click the node, select 'n8nApi' credentials, and connect your account.


3. Execution: Ensure the n8n workflow is active (it is disabled by default). Click 'Execute Workflow' to run the analysis. The results will appear in the output of the final Code n8n node.

When clicking "Execute Workflow" (Manual Trigger): Function: Serves as the starting n8n trigger for the analysis, allowing the n8n workflow to run manually.
n8n (n8n Node): Function: Interacts with the local n8n API to pull metadata and the JSON structure for all active n8n templates. Key Configuration: Requires n8n API credentials and is configured to retrieve all active workflows.

• Find params with affected expressions (Code n8n node): Function: This is the critical logic engine of this n8n workflow. It uses custom JavaScript to parse the JSON structure of all previous n8n nodes, specifically searching for parameters containing expressions that were updated or deprecated in n8n v1 (e.g., minus, beginningOf). Key Configuration: Defines the AFFECTED_EXTENSIONS array and implements recursive search functions.