Hey @ruchi Welcome ot the community !
Your screenshot shows a /form-test/ URL. Open the Form Trigger, click Execute Step, then submit the form that opens while the node is waiting for a submission.
If that still fails, press F12, open Network, submit again, and share the POST request’s status code and Response tab, plus your n8n version. The message you’ve posted doesn’t show the underlying error.
Can you share the workflow, if yes i can help you fix the issue in a better manner.
That 401 means the request was rejected as unauthorized. In Network, click the request showing 401 and share its path and Response text. Is it the POST to /form-test/..., and what’s Authentication set to in your Form Trigger?
With n8n User Auth, loading the form and submitting it are separate auth checks.
Sign back in to n8n on ampworkflow.gevernova.net in the same browser, then close the old form tab and open a fresh test using Execute Step. If that still returns 401, check whether the failed POST has an x-auth-token request header. Just confirm whether it’s present, don’t share its value.
Can you share the workflow JSON with private data removed?
Still facing 401 error , i am just executing the step and want to see result in table and json format in workflow itself . not able to see X-auth-token
Hi @ruchi, Table/JSON output appears after you submit the form; Execute Step starts listening. To isolate the 401, duplicate the workflow, keep the copy unpublished and use dummy data. In that copy, set the Form Trigger’s Authentication to None, click Execute Step and submit the form. Does the data now appear in the node’s output?
Your latest update confirms submission succeeds with Authentication set to None. That narrows the problem to the authenticated submission path; it doesn’t establish the underlying cause.
For Table/JSON output, click Execute Step, complete the Test URL form, and submit it. Execute Step only starts the listener.
If this is an internal form, restore n8n User Auth, sign in on the same n8n hostname in the same browser profile, then start a fresh test.
If the POST still returns 401, ask your n8n administrator to inspect the authentication failure for version 2.35.4. Share the request path, timestamp and redacted response, without cookies or token values.
Keep None only if anonymous submissions are intended. Production submissions are inspected through Executions, rather than appearing live in the editor.