Webstudio
Log in

Join the Webstudio community

Updated 3 months ago

Webhook form not working - form loses "ws--form-id" name value

At a glance

The community member was trying to make a contact Webhook form work when deploying on Vercel. When the website was published on a wstd subdomain, the form worked correctly and sent a POST to n8n. However, when deploying on Vercel, the value for the "ws--form-id" parameter was empty, resulting in an error. The solution was to manually set the "ws--form-id" parameter in the Webhook Form settings, though the community member was unsure why this issue occurred.

In the comments, other community members asked which browser the community member used and requested a link to the deployed website. The community member provided this information, sharing that they had tested the form on various browsers including Edge, Firefox, Opera, Safari, and iOS Opera, and provided a link to one of the first Vercel builds with the issue.

GGiacomo Viganò

Not really an undergoing issue as I managed to solve this.


Context:

I was trying to make a contact Webhook form work when deploying on Vercel. When website was published on wstd subdomain, the form worked correctly and sending a POST to n8n.

This was the payload sent on submit:


Notice the "ws--form-id" parameter is populated with "action".


When deploying on Vercel, the value for "ws--form-id" parameter was empty:


This resulted in an error:


Solution:

Manually set the "ws--form-id" parameter in the Webhook Form settings:



Not sure why this is happening, but I hope helps you debugging and other users with the same headache :)


Love the product btw!

Giacomo

B
G
2 comments·2 replies
BBogdan
Hey, thanks for report. Which browser do you use?
GGiacomo Viganò

Edge, Firefox and Opera on Windows

Edge, Safari and Opera on iOS

BBogdan
Also could you share deployed website please?
GGiacomo Viganò

Sure - here's one of the first Vercel builds with the issue (so no "ws--form-id" manually set): Vercel build

Don't bother the 404 for some assets, all have been fixed in future builds.

Thanks!