Skip to main content

​
What This Node Does

The Rename node changes column names without affecting the values. Use it to make column names more descriptive, fix naming inconsistencies, or match a required schema for downstream systems. [SCREENSHOT: Rename node on canvas showing “Renamed 4 columns”]

​
When to Use This Node

Use the Rename node when you need to:
  • Improve readability - Change “col1” to “customer_name”, “amt” to “total_amount”
  • Match export schemas - Rename columns to match required format for external systems
  • Fix naming conventions - Standardize to snake_case, camelCase, or Title Case
  • Prepare for joins - Rename columns to match join key names in other datasets

​
Step-by-Step Usage Guide

1

Add Rename node to canvas

2

Connect to upstream data

3

Select column to rename

Choose current column name from dropdown[SCREENSHOT: Column dropdown showing existing columns]
4

Enter new name

Type the new column name (e.g., total_amount instead of amt)[SCREENSHOT: New name input field]
5

Add more renames (optional)

Click “Add Another Rename” to rename multiple columns at once[SCREENSHOT: Multiple rename operations]
6

Preview results

​
Tips and Best Practices

Consistent Convention: Choose one naming convention (snake_case, camelCase) and use it throughout your project for better readability.
Rename Early: Place Rename node early in workflow (after Input) to work with clear column names throughout.
Descriptive Names: Use full words, not abbreviations. customer_first_name is better than cust_fname or cfn.
Check for Duplicates: Ensure new names don’t conflict with existing column names. Rename node will error if duplicate names exist.
Batch Renames: Rename multiple related columns in one Rename node (e.g., all customer columns) rather than separate nodes.
Match Downstream Needs: If exporting to a system with specific schema requirements, rename columns to exact requirements to avoid connector issues.