Webhook URLs are suddnely returning a 404

You have to POST JSON data to the webhook. You can’t send a GET request (which is also the same as visiting the URL in a web browser).

You can learn more about Airtable’s incoming webhooks here:

If you’re looking for a GET webhook, you would need to use a webhook automation service like Make.com (which also supports POST requests).

Thanks Scott for that!

It is not obvious from the short description on trigger it needs to be POST. There should be a link explaining their understanding of it.

From quick testing it looks that for example - you cannot send data via query parameters, but sending body in application/json format works like a charm.

It seems it also accepts form data - so you could technically submit any html form data to airtable - which is super cool.

If any Airtable team is watching the threads above info on trigger page, would be super useful!

Thanks Scott for that!

It is not obvious from the short description on trigger it needs to be POST. There should be a link explaining their understanding of it.

From quick testing it looks that for example - you cannot send data via query parameters, but sending body in application/json format works like a charm.

It seems it also accepts form data - so you could technically submit any html form data to airtable - which is super cool.

If any Airtable team is watching the threads above info on trigger page, would be super useful!

As @kuovonne mentioned above, all of this information is already included in Airtable‘s support article on webhooks:

@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. - YouTube

<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.

@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. - YouTube

<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.