How can I update an outdated n8n workflow to eliminate the 'Cannot find name key' error?

Below is one way to address the error "Cannot find name 'key'" when running the workflow:

Why the Error Occurs

The error indicates that somewhere in the workflow’s code, the variable key is referenced without being declared—in other words, the code is trying to use key without a proper definition. This issue is common if the sample workflow (or one of its code nodes) was built against an older version of n8n where variable handling was more lenient, or if a change in n8n’s runtime now requires all variables to be explicitly declared.

How to Fix It

1. Declare the Variable Explicitly:
   Open the code node that contains the reference and add a declaration. For example, if you see the following code:

   JAVASCRIPTCopied
   console.log(key);

   Update it to declare the variable using one of the JavaScript variable declarations. For instance:

   JAVASCRIPTCopied
   const key = 'your-api-key';
   console.log(key);

2. Review the Node’s Logic:
   Verify that the variable is intended to come from a credential or a previous node. If it’s supposed to be dynamically provided:

   • Check if you need to use an expression like {{$json["key"]}} or reference a node’s output.
   • If the key is meant to be injected from credentials, ensure that the credentials are correctly bound to the node using n8n’s credential management system.

3. Update the Workflow Template:
   If the sample workflow originates from an older version, consider looking for a more recent template or updating the code to use best practices for variable declaration and referencing in n8n. Sometimes these updates mean replacing old inline code with a dedicated custom node or using n8n’s parameterized input features.

4. Test the Change:
   After ensuring that every reference to key is properly declared or replaced, run the workflow again to see if the error is resolved.

Example Updated Code Node

Here’s an updated example if the error originated from a code node:

JAVASCRIPTCopied
// Ensure you declare the key variable explicitly.
const key = 'your-api-key'; 
// Replace the constant string with a dynamic value from credentials if needed.
console.log('API Key:', key);

// Proceed with the rest of your logic that uses "key"

Final Thoughts

Updating the workflow by properly declaring the variable should fix the error. If the sample workflow uses credentials or other dynamic values, remember to check that those are correctly configured in your n8n instance. If further errors persist, try comparing the workflow’s logic with the latest n8n documentation or updated versions of similar workflows.

This change should align the workflow with current JavaScript standards and n8n’s requirements, resolving the "Cannot find name ‘key’" error.