-
Notifications
You must be signed in to change notification settings - Fork 47
custom payload not rendering in fulfillment message #4
Comments
What is the request source you're getting? Currently custom payload only supports the following request source: "google", "facebook", "kik", "line", "skype", "slack", "telegram", "viber". Other than that the key will be set to "unspecified". That seems what happened with yours. Furthermore, when you're integrating with certain platform, don't preview them in Dialogflow console, cause it will also set the key to "unspecified". |
Thanks for the quick response. I am not worried about the key, I can handle that as I am using a nodejs client. My issue is that the payload is outside the fulfillmentMessages array. |
Oh sorry, are you talking about |
yh, exactly |
I can't reproduce the JSON response you mentioned in the first comment, either by adding it manually using DIalogflow console or using Dialogflow official NodeJS library. Can you explain more what is the use case here? And what is |
@Sarps I'm getting a similar issue, have you been able to fix yours ? |
I think this issue should be closed due to inactivity. |
When I create a custom payload programmatically and render it, it ends up being outside of the fulfillmentMessages array.
Due to that dialogflow places the payload in data object instead of messages object.
Which is not what I get when I add the payload manually to the intent response inside dialogflow.
Please is there any way that I could force the payload into the fulfillmentMessages array.
Thank you for your good works. This package has really helped a lot.
The text was updated successfully, but these errors were encountered: