Skip to main content
Solved

Voiceflow Integration - Not working as it should with template and throwing errors

  • April 17, 2025
  • 3 replies
  • 50 views
Jennifer_chatbot

I am using the voiceflow to manychat connection template by Omnifusion (linked below) however I’m experiencing a bug somewhere in the pre-made template and I can’t for the life of me figure out where it is or how to solve it. 

I think I’ve pinpointed it to one area of code, however when I’ve validated the code it appears to be fine. Has anyone experienced similar errors? Or do you have experience with this template/connection and can offer assistance? Many thanks!


https://app.manychat.com/flowPlayerPage?share_hash=740143_98c18452de32fe8330e8ae8038d61053bf49369f

 

Best answer by rogerioaraujo

Hello ​@Jennifer_chatbot ,  
Based on the message in the log, it appears to be a mapping error — your JSONPath is incorrect. You can follow the steps below to check:

1. Send a new test request.  
2. Copy the entire response from the "Response Body" field.  
3. Go to the website https://jsonpath.com

As shown in the screenshot below:  
- In field 1, paste the full API response (the one you copied from "Response Body").  
- In field 2, enter the JSONPath you're currently using (for example: `$.variables.user_id`).  
- The mapped value should appear in field 3. If nothing appears, this confirms the mapping error indicated in the log.

To identify the correct JSONPath more easily, you can also paste the full API response into ChatGPT and say something like:  
"Hi ChatGPT, could you please tell me the JSONPath to extract the information from field X?"  
(Replace "field X" with the exact data you want to extract from the API response.)

Let me know if this helped!

    3 replies

    rogerioaraujo
    Forum|alt.badge.img+2
    • rogerioaraujo
    • Flow Scholar
    • 495 replies
    • April 17, 2025

    Hello ​@Jennifer_chatbot ,

    I haven’t used this model yet, but I recommend selecting a test contact and running the action by clicking the "Test Request" button. After that, a response will appear, which may provide clues about what’s happening.

    Please remember to fill in the "processed input" custom field for the selected contact with a value, so that an empty field is not sent to the API.

     

    Feel free to share the response after running the test so we can help you more effectively.

    Jennifer_chatbot
    • Jennifer_chatbot
    • Author
    • Up-and-Comer
    • 1 reply
    • April 18, 2025

    Thank you so much for getting back to me!

    Currently the code is as follows:

    {
      "action": {
        "type": "text",
        "payload": "{{cuf_12840459}}"
      }
    }

    With the processed input being filled with "{{cuf_12840459}}"

    I’ve tested each step and get the 200 OK each time, so I’m unsure where the break is. 

    My logs have the following errors, which I can’t quite pinpoint in the flow

     

     

    rogerioaraujo
    Forum|alt.badge.img+2
    • rogerioaraujo
    • Flow Scholar
    • 495 replies
    • Answer
    • April 18, 2025

    Hello ​@Jennifer_chatbot ,  
    Based on the message in the log, it appears to be a mapping error — your JSONPath is incorrect. You can follow the steps below to check:

    1. Send a new test request.  
    2. Copy the entire response from the "Response Body" field.  
    3. Go to the website https://jsonpath.com

    As shown in the screenshot below:  
    - In field 1, paste the full API response (the one you copied from "Response Body").  
    - In field 2, enter the JSONPath you're currently using (for example: `$.variables.user_id`).  
    - The mapped value should appear in field 3. If nothing appears, this confirms the mapping error indicated in the log.

    To identify the correct JSONPath more easily, you can also paste the full API response into ChatGPT and say something like:  
    "Hi ChatGPT, could you please tell me the JSONPath to extract the information from field X?"  
    (Replace "field X" with the exact data you want to extract from the API response.)

    Let me know if this helped!


    Community Terms & ConditionsCookie settingsAccessibility statement