Skip to main content

In my ManyChat webhook the field named continue won’t save to its custom field, while the others work fine.

{
  "output": {
    "response": {
      "part_1": "¡Sí, enviamos en Miami-Dade! 🚚",
      "part_2": "Ofrecemos pick-up y entrega.",
      "part_3": "¿Quieres info o hacer un pedido? ¡Dime!",
      "continue": "continuar_proceso"
    }
  }
}

What happens

JSON key

Saves?

part_1

✅

part_2

✅

part_3

✅

continue

❌

 

What I’ve checked

  • Field name & type are correct.

  • Renaming continue to something else (e.g., next_step) works.

  • Rebuilt the Bulk Set Data step and cloned the flow—same result.

Ask: Is continue a reserved word in ManyChat, or is there another fix besides renaming the key? Any tips appreciated!

 

 

​@nocodedude I’ve used a lot of external requests and whenever I’ve had an error, it’s always been that the mapping is wrong.

Having said that, and since it looks like you know what you’re doing, I suggest you try this…

Create a simple Make.com scenario that takes a webhook from Manychat a replies with 200 OK with:

{
   "continue": "continuar_proceso"
}

If that fails, then try with something like:

{
   "xx_continue_xx": "continuar_proceso"
}

 

If you find that one works and the other doesn’t, then you’ll have isolated the issue - and you can open a ticket with Manychat with a simple and easy-to-reproduce scenario.

Hope this helps!

Reply


Community Terms & ConditionsCookie settings