Can someone explain to me why when I’m making a <<START: >> block in a webhook step… that I have to include the trailing comma in the object I’m making.
Example
[
<<START: Analyses_Need_Redo[WklyAiAnalysis_ID]>>
{
"source_id":"<<[WklyAiAnalysis_ID]>>"
},
<<END>>
]
If you don’t include that comma after the closing curly bracket, you get the following error when you try and run the automation
So… I literally have to do a technical thing (that should be system-side) otherwise I get an error.
But… then my object has a trailling comma, and it breaks the JSON parser.
And I can’t work around the problem by setting the content type to plain text
So I’m forced to use JSON, which can be sometimes automatically parsed by certain systems when it comes in
- Meaning: i can’t catch the malformed object and fix it
Who built this system? Are they still working on the team? Can they go in an fix this please!?! 
- SEVERITY: Critical
2 Likes
Yes, I can confirm that is a very critical issue
I cannot send data to Make.com using a webhook because the system add an extra comma at the end of a << If: >> …….<< Endif >> condition in the JSON body template
3 Likes
@MultiTech
This MUST be a bug that has been introduced sometime in the past year or so.
I have JSON templates almost exactly as your example that DO NOT have the trailing comma you show. They worked flawlessly for a couple years though I have not used them actively in over a year. So when that bug was introduced, I couldn’t say.
2 Likes
@MultiTech
I took a closer look at syntax. I don’t know if it matters but I do remember the formatting was a little unforgiving.
I am noticing in all my API JSON templates I have a space after the colons. Yours doesn’t. It’s worth the try!!
And actually…I lied. My JSON is not exactly the same… I have a “Rows” designation. Don’t you need that or something similar to differentiate one row value from the next?
Yes, this is an AppSheet API call.
{
“Action”: “Add”,
“Properties”: {
“Locale”: “en-US”,
“Location”: “<<42.80890903597787, -71.6389241275992>>”,
“Timezone”: “Eastern Standard Time”,
},
“Rows”: [
<<START: [Add_Items][Item_ID]>>
{
“Field 1”: “<<[Column 1]>>”,
“Field 2”: “<<[Column 2]>>”,
“Field 3”: “<<[Item_ID]>>”
}
<<End>>
]
}
1 Like
Your showing the full object, which you make when you’re using the API externally.
I’m using the internal API, and only showed you the “body” entry - which is the “Rows” object.
I’ve tried some alternate configs, they all require that trailing comma - otherwise automation throws an error.
1 Like
I see!! Did you try inserting a space after the colon? I remember the formatting being finicky and slim on annoucing the issue.
