JSON Template not being read sometimes by the Webhook

Hello Glide Community,

I have set up a webhook in Glide that sends a JSON body to Make. The JSON body is generated from a JSON template column in a Glide table.

The problem is that sometimes the JSON template is read and processed correctly, while other times it is not and it results in the webhook as a empty body.

The JSON template has two variables, whose values are generated following an “add row” action performed by the user in a table different from the one containing the JSON template.
Once the row is added, a die is rolled and a multiplier is generated.
The multiplier is brought into the JSON template table using a single value column, and then, through a math column and several if-then-else conditions, the values that fill the JSON template are generated.

Observing the behavior of the JSON template from the data section in Glide, it seems to always function correctly and updates very quickly when the variables change.

I have also added a 15-second delay to see if the issue could be due to insufficient time for the template to update, but I noticed that sometimes with a 15-second delay it doesn’t get read, while other times with a 5-second delay it does get read. So it doesn’t seem to be a timing issue.

What could be the possible causes of this issue?
Any insights or advice would be greatly appreciated.

I have suspected for a while that the JSON Object and JSON Template columns are not 100% reliable when used in combination with webhooks.

Here is something to try: replace your JSON Template column with a regular template column to create the JSON payload, then send that instead. I’ll be interested to hear how that works out.


Now with the regular template column, it seems that the webhook reads the body 100% of the time (after 5 tests), but I get the following problem in the Create JSON module in Make.

This is what Make Webhook receives:

I believe it is due to the numeric value, maybe because my numeric value uses a comma. When using the JSON template column it automatically becomes a point, but with the regular template it remains a comma, and the JSON results invalid.

To work around the issue, I set the numeric value without decimals (so the comma should no longer be present because the number is an integer), but the issue persists.

Try removing the Create JSON module from the scenario path, and pass the payload directly from the webhook to the HTTP module. Don’t ask me to explain why, but I think that will work.

Please help me to set the request content (previously I was using the resulting string from the Create JSON module).

I tried to set it this way, but I get the following error:

That request content looks incorrect. Can you try pointing it to the “Body” level so it reference everything in the body?

1 Like

Hey @ThinhDinh

this is the error I receive if I fill the request content with the “body” variable

This is what the webhook passes to the HTTP module:

Can you show the payload that is sent from Glide? (you can copy it from the action run log)

The structure of your mutations looks a bit off.


Yeah, your mutations are not constructed correctly. Compare what you have to what was created by the JSON Template column. They should be the same. You probably need to adjust your template column.

Actually, are you feeding a lookup column into the template?
If you are, that’s probably the issue. When constructing the JSON manually in this way, you should use a joined list. I know that contradicts what I told you earlier, but it’s a different method. Confusing, I know…

1 Like

This is what I was most interested in. Once you get the full flow working, can you please let me know if it continues to reliably send the full payload 100% of the time?

Ok, it was my fault… I was missing the fact that also the JSON body template needed to be converted to a regular template.

Now it works perfectly!!

After about 20 tests, the payload was sent correctly 100% of the time. I will update you if it fails in any situation.

Thanks again so much!:pray:


Great to hear!

1 Like