Self-Hosted n8n Workflow Form Trigger Fails to Load

Below are a few steps you can try to troubleshoot the Form Trigger node showing an empty/non-responsive form:

1. Verify Node Configuration

• Ensure that the Form Trigger node is configured correctly (e.g. form fields, title, etc.).
• Confirm you’re toggling between the Test URL and Production URL appropriately (remember that production form submissions won’t show the workflow data in the editor).

2. Check Workflow State

• When using the Test URL (via Test Step or Test Workflow), ensure the workflow isn’t already active.
• If you’re testing and also have an active production version, consider disabling the production workflow temporarily for testing.

3. Examine Browser and Network Environment

• Try opening the Test/Production URL in a different browser or in incognito mode to rule out caching or plugin issues.
• Open your browser’s developer tools to check for any console errors or network issues that might indicate a problem rendering the form.

4. Review Docker Logs

• Check the Docker container logs (using Docker Desktop’s log viewer or via the command line) for any error messages or warnings during startup or when the form URL is requested.

5. Update Version (if possible)

• Version 1.70.3 is stable, but if nothing surfaces in the steps above, consider testing on a more recent release. There may be fixes or improvements related to the Form Trigger in later versions.

These steps cover the common areas where misconfigurations or environmental issues might cause the form trigger page not to load as expected. Let me know if you need further details on any of these troubleshooting steps.