Help

Upcoming database upgrades. to improve our reliability at 03:30 UTC on Feb. 25 / 7:30pm PT on Feb. 24. Some users may briefly experience slow load times or error messages. Learn more here

Webhooks and dynamic JSON key/value pairs

Topic Labels: Automations
Solved
Jump to Solution
751 2
cancel
Showing results for 
Search instead for 
Did you mean: 

I am experimenting with Webhooks to move data back and forth between bases.

I just want to make sure what I am seeing/doing is necessary.

When I setup a test POST from an external tool to test the webhook, any data elements defined the JSON are created as values in javascript editor. However, I would prefer to read the entire json object as new fields may become necessary.

What I did was create an object that looked like this:

{ "theData" : "Anything" }

I tested the webhook and “theData” was available to the script editor.

I then created a more representative object like this:

{ "theData" : {
   "fieldOne" : "Some data",
  "fieldTwo" : "More data",
  "fieldThree" : "and even more data"
}
}

This works fine and my code is working. Is this how I have to set it up?

If I send the second structure as a test, the script editor forces me to select one of the nested fields. I cannot select the top level key.

It’s not the worst thing to have to do but it does seem like a bit of an extra step.

Thanks.

1 Solution

Accepted Solutions

That’s unfortunately the current limitation of the webhook trigger. However, you can actually work with that and get what you want.

In short, you stringify your main object, then stringify it again when inserting into the body of the request. Here’s a quick example that I just tested:

const hookUrl = "https://hooks.airtable.com/workflows/v1/genericWebhook/..."

const myObject = {
    "fieldOne": "Some data",
    "fieldTwo": [1, 2, 3],
    "fieldThree": {
        first: true,
        second: "blah",
        third: 19
    }
}
const options = {
    method: "POST",
    headers: {
        "Content-Type": "application/json"
    },
    body: JSON.stringify({
        data: JSON.stringify(myObject)
    })
}

const response = await remoteFetchAsync(hookUrl, options)
if (response.ok) {
    output.text("OK")
} else {
    output.text("Not OK")
}

On the receiving end, you only have a single data item to pass to your script, which is the string version of your original object. Turn it back into the original object using JSON.parse():

const {data} = input.config()
const myObject = JSON.parse(data)
console.log(myObject)

Screen Shot 2021-12-10 at 4.28.53 PM

See Solution in Thread

2 Replies 2

That’s unfortunately the current limitation of the webhook trigger. However, you can actually work with that and get what you want.

In short, you stringify your main object, then stringify it again when inserting into the body of the request. Here’s a quick example that I just tested:

const hookUrl = "https://hooks.airtable.com/workflows/v1/genericWebhook/..."

const myObject = {
    "fieldOne": "Some data",
    "fieldTwo": [1, 2, 3],
    "fieldThree": {
        first: true,
        second: "blah",
        third: 19
    }
}
const options = {
    method: "POST",
    headers: {
        "Content-Type": "application/json"
    },
    body: JSON.stringify({
        data: JSON.stringify(myObject)
    })
}

const response = await remoteFetchAsync(hookUrl, options)
if (response.ok) {
    output.text("OK")
} else {
    output.text("Not OK")
}

On the receiving end, you only have a single data item to pass to your script, which is the string version of your original object. Turn it back into the original object using JSON.parse():

const {data} = input.config()
const myObject = JSON.parse(data)
console.log(myObject)

Screen Shot 2021-12-10 at 4.28.53 PM

Thanks… Yep… I sent the complete object after testing it without the additional key/pairs and it works. Just of a strange feature.