Describe the problem/error/question
When I rename a node to match its default integration name (e.g. Postgres or HubSpot), and then make any change in the parameters or operation, the node name gets automatically replaced with the selected operation’s label — like "Get a deal" or "Delete table or rows".
This only happens when the node label is equal to the integration name. If I use a custom name like "DB - Postgres" or "HubSpot Deals", the name remains intact.
Is this intended behavior? Can it be disabled? It breaks naming consistency in larger flows where node naming is important for readability.
What is the error message (if any)?
There is no error message — just unexpected UI behavior.
Please share your workflow
This happens with any workflow — not tied to a specific one. Here’s a simple example:
1. Add a PostgreSQL node
2. Rename it to "Postgres"
3. Change the operation to "Delete"
4. Node is renamed to "Delete table or rows"
Repeat with HubSpot:
1. Add a HubSpot node
2. Rename it to "HubSpot"
3. Change the operation to "Get a deal"
4. Node is renamed to "Get a deal"
Video: https://drive.google.com/file/d/1G4GuqK3eJTAfHjga2ncY7RS2CwpUaq9y/view?usp=sharing
Share the output returned by the last node
N/A — issue is related to UI behavior, not execution or data.
Information on your n8n setup
- n8n version: 1.104.1
- Database: PostgreSQL
- n8n EXECUTIONS_PROCESS setting: own
- Running n8n via: Docker (self-hosted)
- Operating system: macOS (M1 Pro)