The community member is having trouble with the action URL in a form they created, where they are trying to send a webhook to n8n but it's not working. They noticed that the "action=" attribute is not present in the code when they publish the site. Other community members suggest trying a webhook form instead of a regular form, and note that the real action URL is added on the server-side to hide the authentication token. The community member tests a new webhook form but still encounters issues, and they eventually figure out that the problem was likely due to the way they inserted the URL in the action field. They delete and re-enter the URL, and it starts working. The community member also asks how to add a form success URL (thank you page) instead of a standard message, and a community member provides a workaround for that.
Friends, tell me what is the problem with action URL in forms I made a simple form with one field and a button, I try to send a webhook to n8n - and it doesn't go away. in the action field I write the necessary webhook URL I publish the site - but there it is not “action=” in the code..... what the hell? do the forms even work?
Thanks for your patience friends! I think I figured it out, the problem was probably in the way the URL was inserted in the action field. I deleted everything and put it back together again and it worked.
No it's probably a minor bug, but because I'm not yet familiar with webstudio. I'm not sure I can replicate it. I first tried adding a URL to the action field via expression editor, when it didn't work I deleted the expression and added in quotation marks again it didn't work, and then without quotation marks and changed the url a few more times. Probably after the first two operations something remained and although in the visual environment everything looked right. I deleted the form and created a new one, then it worked.
and another question how to add form success URL (thank you page) to use it instead of a standard message?
success message is part of the component, you can drop there any instance and even make it fulscreen if needed, but if you want a separate page, currently requires this workaround: