Form Webhook: Record ID as Default URL Paramenter

We are excited to inform you that we have added the record ID as a default URL parameter in the webhook regardless if the webhook is from Airtable field or a static URL in the extension setting page. In this way, there will be an indicator of which record triggers the webhook.

Your feedback is valuable to us, and we would love to hear any comments or suggestions you may have. Please do not hesitate to share your thoughts by commenting below or contacting us via chat.


Hi Paulo

CAn it be possible to add some more information in the Webhook body? Like fields on the form itself. Examples: Name, email, phone, etc


Hi @ultimate1984,

Thank you for your feedback. Can you provide more information about your use case. A real-life example of the problem that you are trying to solve would be ideal.


A much needed feature and a first step in being able to send more data in the webhook body - a feature that I’ve previously requested. It would cut out having to transfer data via other means.

1 Like

Hi Paulo, I really think the screen shots and use case is well explained above and understandable. I don’t know what more to add here. It is a very common thing for webhooks to carry body information and headers. So it should not be a big thing to add the feature? At this stage the webhook can only be used as a trigger, and doesnt carry any usable information in my own automations actions like Zapier or Make for example.

Hi Silisols. Yes I agree, this should be a standard feature of any webhook to be able to carry body information in a Json format, just like the header inforation.

I think it would be helpful to be more specific with the feature request, so I’ll try to break it down. I believe what people are asking for, which I would find useful as well, is to automatically send all the fields with their corresponding values from the form that has just been submitted as a body alongside the webhook. The webhook alone is great for text but not ideal for other data types. The use case is to save on extra steps of calling other external actions such as Make to get all the data that has just been submitted with an Airtable Get Record since we would usually only send the Record ID on the webhook URL parameters. Theoretically, you could send all the data through the webhook as a string with the help of an Airtable formula field, but this is obviously not ideal as not all systems would accept those strings and be able to convert them to the data type they’re supposed to represent, such as numbers, dates, arrays, or objects.


Thank you for your input. I will forward this information in the created ticket. We will keep you updated through this channel.

Thank you for the thorough explanation Brian