Curly Brackets and my chatbot requests

​@NIgefire click on the custom field in the JSON body (the blue custom field bubble) and check the ‘Encode to JSON’ option.

This should solve your problem ;)

Alternatively, you can enclose the user field with “ ” (but the encode to JSON option is better!)

Let us know if this works!

I get this 

​@NIgefire what’s in the ‘body’ section?

Thanks for the follow-up.

I have followed your instructions to “remove the brackets and then encode as JSON,” but unfortunately, this approach is not working as expected. When we do this:

{
  "question": ChatGPT_Question
}

…the preview throws an Invalid JSON error. If we try wrapping the variable in quotes like this:

{
  "question": "ChatGPT_Question"
}

…it treats "ChatGPT_Question" as literal text, not the dynamic variable value — so it just sends the string "ChatGPT_Question" instead of the user’s actual input.

We've also tested inserting the variable using the + Add a Field method. This auto-wraps the variable visually (with the green highlight), but ManyChat still fails to format it with the correct curly bracket syntax ({{variable}}) — and it continues to trigger the Invalid JSON error in the preview panel.

It seems that ManyChat’s internal variable rendering either:

• Doesn’t evaluate the inserted variables correctly when inside a JSON object, or

• Fails to encode the data properly unless the entire payload is dynamically structured — which defeats the purpose of a static JSON template.

Could you please clarify:

1. What is the correct way to dynamically insert user inputs into a JSON POST body, without breaking the syntax?

2. Should the fields inserted using the + Add a Field button be auto-wrapped in quotes or not?

3. If curly brackets and manual wrapping are not allowed — how do we trigger variable rendering that actually sends dynamic values?

Happy to provide additional screenshots or test results if needed — but at this stage, it seems like the builder UI and the webhook preview are misaligned in how variables are parsed.

Thanks,

​@NIgefire this is what it should look like:

1. The user field is added with the {+} link
2. It shows up as a blue bubble on the UI
3. When you click on it, make sure you have the ‘Encode to JSON’ option checked

This, along with a correct JSON structure, works 100% of the time,

​@NIgefire if you share a screenshot of the ‘Body’ section I’ll most likely be able to tell you what’s wrong with it ;)

Thanks, got that sorted and realised I dont have the return flow working, May get back to you

N>