n8n - 💡(How to fix) Fix Form Trigger: Custom "Form Path" resets to random UUID on JSON re-import [1 comments, 2 participants]

Describe the problem/error/question

When exporting a workflow as JSON and re-importing it (e.g. as part of a local backup/edit workflow), the Form Trigger node's custom "Form Path" is not preserved. Instead, it gets reset to a randomly generated UUID-like value.

This is inconsistent with the behavior of Webhook nodes, where the custom path is correctly preserved after re-import. Since the Form Path determines the public-facing URL of the form, this forces manual reconfiguration after every re-import.

Steps to reproduce:

1. Create a workflow with a n8n Form Trigger node
2. Set a custom Form Path (e.g. my-custom-form)
3. Export the workflow as JSON
4. Delete or overwrite the workflow and re-import the JSON file
5. Open the Form Trigger node → Form Path is now a random UUID instead of my-custom-form

Expected behavior: The custom Form Path defined in the JSON file should be preserved after re-import, just like Webhook paths are.

Actual behavior: The Form Path is reset to a newly generated UUID on every re-import, breaking existing form URLs and requiring manual reconfiguration.

What is the error message (if any)?

No error message — the import succeeds silently, but the Form Path value is overwritten with a new UUID.

Debug info

core

• n8nVersion: 2.17.3
• platform: docker (self-hosted)
• nodeJsVersion: 24.14.1
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: enterprise (production)

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
• isTouchDevice: false

security

• secureCookie: false

Generated at: 2026-04-30T15:11:49.685Z