Webhook Form - 405 Method Not Allowed

It's on the Amazing 404 page.
https://apps.webstudio.is/builder/7cd26c20-6f60-49fa-b723-af32384798ed?authToken=01f1fd74-88e9-43e9-aece-23ccafdb4189&mode=preview

I duplicated the page, changed the code to 200 and it works.

So webhook forms don't seem to work with 404 pages if I get it right.

The idea behind a webhook form on a 404 page, was to prefill the url in there and ask the user to send a heads up. So that I could keep track which pages people go to that I might have accidently deleted.

Hi! Not sure you need to add POST Method with Webhook form (not sure that the problem)

I gonna make a test on my side

Webhook shouldn't need a method, its always a POST, but there should be no error either

Never seen anyone doing this. Since you could just see it in analytics

I like to get an email notification so I can fix it right away when it happens

I'll try removing method to see if that works

You can try, for example this page that does not exist:
https://skincms.com/discord

Not really. It's configurable and "get" by default.
Always post is our internal n8n request.

you mean its get between webstudio and webstudio worker, but its post when it lands on n8n

In the Webstudio tutorial it shows POST as well.

Worker fetch is invoked with whatever method user provided. Though since we always passing json as body, GET just would not work. So only POST and PUT make sense.

In the future we need to support GET and DELETE methods by writing form data into url search params like browsers do.

Any idea why this 405 error might happen?

Did you try to test with curl?

No, how do I do that?

curl -X POST your_url

in terminal

Never done that before, but it works yes

I will take a look later today

Thank you Bogdan!

Hey, try to republish and submit form again

We released a fix, hope will work

Great, but unfortunately it doesn't work yet

I can confirm, still getting the error

Ok, will check

rechecked, I had wrong hook url, it works now perfectly fine

@Ronald from 360Creators if you had this issue, check your airtable hook url and make sure you published before testing