Help

Webhook payload - still limited access to nested data?

Topic Labels: Automations
5118 20
cancel
Showing results for 
Search instead for 
Did you mean: 
Luke_Concannon
6 - Interface Innovator
6 - Interface Innovator

Tena Koutou!

I got momentarily excited by the received webhook trigger in automations (old news I know, just got round to it seeming like a time saver!) only to learn that there is limited access to nested data within the json payload…

I’m sending a payload via webhook from Typeform => Airtable. Works great. I just can’t access the nested data I need. super frustrating. Seems like a fairly standard issue feature to be able to access nested data within a JSON object.

Has there been any update to this? Anyone have any work arounds that dont involve third parties? I’m happy proxying the webhook through vercel serveless function but just seemed like a quick win to manage it in airtable.

Any advice hugely appreciated!
Luke

20 Replies 20

You should be able to write a JavaScript to access the nested data.

Otherwise, you would need to use a 3rd-party service. For a no-code webhook solution, I personally use Make:

There has been no update to this as far as I know.

If you know the exact shape of the data, you can use individual input variables to get a specific nested value.

But overall, you are correct that you need some third party system. One third party option is to JSON stringify the payload and store that string in a single key. (Essentially stringifying twice.) Then have a script parse the JSON from that single key.

Should you? Yes. Can you? No.

The entire point of inbound webhooks is to avoid middleware that increases solution complexity and latency.

This is only possible if you control the inbound hook. The entire point of supporting webhooks is to enable arbitrary conveyances of data payloads, many of which are predictably complex and varied such that the webhook listener must be able to process the payload with action scripts.

While this seriously critical requirement continues to make integrations vastly more difficult than they should be, Airtable focuses on improvements like these.

image

I get that your complaint is with Airtable’s limitations, but if it’s our only solution at the moment, then that’s all we can do for now. :man_shrugging:

I’m not dismissing your very legitimate complaint about Airtable’s engineering focuses.

Also, it looks like incoming webhooks are still in Alpha. At least that is what the user interface still says. This issue might be one of the reasons why it is still in Alpha.

Yeah, I’m good with that as an answer, but after 14 months in “alpha” testing and tens of thousands of actions depending on it, I’m less inclined to be kind. After all, this shortfall is simply missing the ability to map the root of the JSON payload into a field or a parameter; all other elements are mappable, just not this one.

I see this more as an indication that it is a low priority for Airtable, not as a need for more testing. I’m guessing that Airtable knows that this is an issue, but that it is not their focus, and so they are choosing to leave it in alpha because they know they can’t reasonably take it out of alpha without implementing this feature and they don’t want to spend their resources there now.

@ScottWorld - That’s clearly because you have some sort of commercial relationship with them though right? You’ve been recommending this third party on every thread I read yesterday.