@ScottWorld yes, clearly stated in the docs. I am thinking reducing functionality of webhooks to one http method is non-obvious choice, so more people might get caught.
I just tested and it can be well used to capture submission from ANY html form! For example something with more custom design, hidden input variables or for people struggling to capture forms on Wordpress sites. This is super easy just to add webhook url in action and method=“POST”
I just did a quick example here: Mind blown! Send data from ANY HTML form to Airtable with the new webhook automation trigger. - YouT...
<form action="https://hooks.airtable.com/workflows/v1/genericWebhook/XXXXXXXX" method="POST">
<label for="fname">First name:</label><br>
<input type="text" id="fname" name="fname" value="John"><br>
<label for="lname">Last name:</label><br>
<input type="text" id="lname" name="lname" value="Doe"><br><br>
<input type="submit" value="Submit">
</form>
A question though and I don’t see this in the docs - Anyway to customize response instead {success: true} ?.
In the use case above it would be super useful to reply with 302 and Location header to e.g. a “Thank you” page.
