How to Find and Replace Data Properties in n8n Workflows

When building complex data pipelines in n8n, you'll inevitably encounter situations where you need to update multiple references to database tables, column names, API endpoints, or other data properties across your workflow. Whether it's due to schema changes, API updates, or evolving business requirements, manually updating each node can be time-consuming and error-prone.

This guide will walk you through an efficient method to bulk update data properties in your n8n workflows using Visual Studio Code's powerful find-and-replace functionality.

Why This Method Works

n8n workflows are essentially JSON configurations that define nodes, connections, and data transformations. By exporting portions of your workflow as JSON, you can leverage any text editor's search-and-replace capabilities to make bulk changes quickly and accurately.

The Step-by-Step Process

1. Select the Nodes You Want to Update

Hold Ctrl (or Cmd on Mac) and click each node that contains the properties you need to update
Alternatively, drag to select multiple nodes at once
Focus on nodes that interact with your data sources (database nodes, HTTP requests, Set nodes, etc.)

2. Copy the Selected Nodes

Right-click and choose "Copy" from the context menu
Or use the keyboard shortcut Ctrl+C (or Cmd+C on Mac)

This copies the node configurations to your clipboard as JSON.

3. Open Visual Studio Code

Create a new file (Ctrl+N or Cmd+N)
This will serve as your temporary editing space

4. Set Up JSON Formatting

Look at the bottom-right corner of VS Code
Click on "Plain Text" (or the current language mode)
Type "JSON" and select it
This enables JSON syntax highlighting and formatting

5. Paste and Format Your Workflow Data

Paste with Ctrl+V (or Cmd+V)
Format the JSON for readability:
- Shift+Alt+F (Windows/Linux) or Shift+Option+F (Mac)
- Or right-click and select "Format Document"

6. Perform Find and Replace Operations

Use VS Code's powerful find-and-replace:

Basic Find and Replace:

Press Ctrl+H (or Cmd+H)
Enter your old value in "Find"
Enter your new value in "Replace"
Click "Replace All"

Common Use Cases:

// Changing table names
Find: "users_table"
Replace: "customers_table"

// Updating column references
Find: "user_id"
Replace: "customer_id"

// Modifying API endpoints
Find: "api/v1/users"
Replace: "api/v2/customers"

// Updating response property names
Find: "firstName"
Replace: "first_name"

Advanced Find and Replace with Regex:

Find: "table_(\w+)"
Replace: "new_table_$1"

7. Copy the Updated JSON

Select all (Ctrl+A) and copy (Ctrl+C).

8. Update Your n8n Workflow

Delete the original nodes
Paste the updated nodes (Ctrl+V or Cmd+V)

n8n will automatically recreate them with updated configurations.

9. Test and Verify

Reconnect any broken connections
Check node configurations
Run a test execution
Verify data flows correctly
Check logs for errors

Pro Tips and Best Practices

Before You Start

Backup your workflow
Document your changes
Test in a dev environment first

During the Process

Use descriptive find-replace terms
Preview replacements
Work in small batches

Advanced Techniques

Use VS Code's multi-cursor editing
Leverage regex patterns
Enable "Match Case" and "Whole Word" for precision

Common Scenarios and Examples

Database Schema Changes

// Old schema
"tableName": "user_profiles"
"columns": ["user_id", "user_name", "user_email"]

// New schema
"tableName": "customer_profiles"
"columns": ["customer_id", "customer_name", "customer_email"]

API Endpoint Updates

// Before
"url": "https://api.example.com/v1/users/{{$json.id}}"
"headers": {"Authorization": "Bearer {{$json.userToken}}"}

// After
"url": "https://api.example.com/v2/customers/{{$json.id}}"
"headers": {"Authorization": "Bearer {{$json.customerToken}}"}

Troubleshooting Common Issues

Nodes Don't Appear After Pasting

Check JSON validity
Ensure complete node definitions were copied

Workflow Connections Break

If node names changed, reconnect manually
Try keeping names unchanged

Execution Errors

Verify property names and API endpoints
Test nodes individually

Conclusion

This method of using VS Code for bulk find-and-replace operations in n8n workflows can save hours of manual editing. Be methodical, test thoroughly, and always maintain backups. With practice, this workflow will become second nature, making you more efficient at maintaining and updating your n8n automation pipelines.