> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nrev.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Rename Column

> Give your columns the glow-up they deserve — rename anything for clarity, alignment, and better downstream automation.

## What It Does

* Renames one or more columns — finally, goodbye `col_1` 👋
* Helps you standardize naming conventions across datasets
* Keeps column order and all data intact
* Silently skips anything invalid or unnecessary — no drama

> 🧠 Think of this as your “naming hygiene” node — perfect for tidying before merges, exports, or sending data to Salesforce/Zapier/HubSpot.

***

## 🏁 Getting Started

<Frame>
  <img src="https://mintcdn.com/nurturev/mHCimB8YAP--VMGj/images/Rename%20Column%20node%20configuration.png?fit=max&auto=format&n=mHCimB8YAP--VMGj&q=85&s=70bea2a3d580622c5e4c0fd2521d3843" alt="Rename Column node configuration" style={{ borderRadius: '0.5rem', width: '100%', margin: '1.5rem 0' }} width="1180" height="1664" data-path="images/Rename Column node configuration.png" />
</Frame>

<Steps>
  <Step title="Drop It In">
    Add the **Rename Column** node right after your data pull or cleanup step.
  </Step>

  <Step title="Map Old to New">
    For each column, pick the one you want to rename and type in its glow-up version.
  </Step>

  <Step title="Rename More (Optional)">
    Add more rename pairs if your dataset needs a full wardrobe change.
  </Step>

  <Step title="Run It">
    Boom — your data’s now wearing its name badge correctly. Send it downstream to whatever tool’s next.
  </Step>
</Steps>

***

## Inputs

### 🛠️ Required Fields

* **Columns to Rename (✅)**\
  For each rename, define:
  * The original column name (from your input dataset)
  * The new column name (what you actually want it called)

> ✅ Pro tip: Match your naming conventions across ops tools (e.g., `email_address` instead of just `email`) to avoid breakage in merges or automations.

***

## Output

You get back a table that’s 100% identical in structure — except for those sweet new column names.

* Rows: unchanged
* Column order: untouched
* Only names updated, no data harmed in the making

***

## 🚀 Use Cases in the Wild

| Situation                           | How Rename Column Helps                       |
| ----------------------------------- | --------------------------------------------- |
| Prepping data for Salesforce import | Rename `phone_cleaned` → `Phone`              |
| Aligning schemas before a Join      | Rename `lead_id` → `contact_id`               |
| Cleaning up scraped web data        | Rename `col_1`, `col_2` to actual field names |
| Naming for reporting clarity        | Rename `Q1 Rev` → `revenue_q1`                |

***

## ✨ RevOps Pro Tips

<Tip>
  Standardize column names before merging — inconsistent names are the silent killers of automated workflows.
</Tip>

<Tip>
  Rename to match your CRM or BI tools (e.g. `contact_email`, `owner_id`) so handoff between systems is clean.
</Tip>

<Tip>
  You can skip cleaning ahead of time — we’ll gracefully ignore columns that don’t exist.
</Tip>

***

## ⚠️ Gotchas (Avoid These)

<Warning>
  You can’t rename multiple columns to the **same** name — that’ll block the run.
</Warning>

<Warning>
  Renaming to the **same name** does nothing — we skip it quietly so you don’t waste steps.
</Warning>

<Warning>
  Columns that don’t exist in the input? Also skipped. No crashes, no panic — just smart handling.
</Warning>

***

## 🛠 Troubleshooting

| Symptom              | Possible Cause                          | Fix                                               |
| -------------------- | --------------------------------------- | ------------------------------------------------- |
| Column didn't rename | You may have a typo or it doesn’t exist | Check the input schema first                      |
| Nothing changed      | All rename pairs were no-ops            | Make sure your "new" names are actually different |
| Clash of new names   | Two columns renamed to the same name    | Pick distinct names for each                      |

***

## 📝 FAQ

<AccordionGroup>
  <Accordion title="Can I rename multiple columns at once?">
    Heck yes — rename your whole schema if needed. Add as many as you like.
  </Accordion>

  <Accordion title="Will the column order change?">
    Never. We’re not that kind of node.
  </Accordion>

  <Accordion title="What if a column doesn't exist?">
    No problem — we skip it quietly and keep moving. Resilient by design.
  </Accordion>

  <Accordion title="Can I rename to the same name?">
    Technically yes, but it’ll be skipped. No warnings, just efficiency.
  </Accordion>
</AccordionGroup>

***

## 💰 Pricing

> The Rename Column node is **free**. Rename with confidence — no credits required.

***

<p style={{ fontSize: '1rem', fontWeight: 'bold', marginTop: '1.5rem' }}>
  Good column names aren’t just vanity — they’re operational clarity. Rename with confidence and keep your data flows clean, smart, and aligned. 🧼
</p>