Hello n8n community,
We need guidance on safely repairing an existing workflow in self-hosted n8n 2.30.4, without risking unintended changes.
Current situation
- The workflow is inactive and unpublished.
- It currently contains 26 nodes.
- One Data Table node (
n8n-nodes-base.dataTable, typeVersion 1.1) is missing. - The original missing node has the ID
b4-17. - We have verified backups of the current workflow and the original 27-node design.
- Only the missing node and its two connections should be restored.
- All existing nodes, credentials, webhook paths, workflow settings, and the workflow identity must remain unchanged.
A previous attempt to paste a partial JSON fragment into the editor unexpectedly changed the workflow title. We stopped and subsequently restored the intended title.
We do not want to repeat this approach without reliable safeguards.
Questions
1. Restoring a node with its original ID
Does the native n8n 2.30.4 editor support inserting or restoring a node while preserving its exact original JSON ID (b4-17)?
If this is not supported, is preserving the original node ID technically necessary, provided the node name, parameters, expressions, and connections remain correct?
Are there any internal references or mechanisms that could depend on this ID?
2. Version conflict protection
Does n8n 2.30.4 reliably protect against concurrent modifications when saving a workflow through the editor?
For the API endpoint PUT /api/v1/workflows/{id}, does versionId provide effective optimistic locking in this specific version?
The current API documentation refers to optimistic locking, but versionId also appears as read-only in the update schema. We would appreciate clarification on the actual supported behavior.
3. Safest officially supported repair procedure
What is the recommended approach for restoring exactly one missing node and its two connections in an existing inactive workflow?
Our priorities are:
- Preserve the existing workflow ID and title.
- Preserve every existing node and unrelated connection.
- Preserve credentials, webhook paths, and security settings.
- Prevent unintended activation or publishing.
- Create a complete before-and-after JSON comparison.
- Avoid overwriting concurrent changes.
Would you recommend a controlled editor operation or an API update for n8n 2.30.4?
We would especially appreciate references to official documentation or the relevant version-specific source code.
For security reasons, we are not publishing our complete workflow JSON, API keys, credentials, or internal infrastructure details.
Thank you for your help!