relying on the existence of `msg.payload.chatId` in "Telegram Sender" prevents from using some other nodes about node-red-contrib-chatbot HOT 3 CLOSED

Thanks @cowchimp!

Can you tell how your flow is configured exactly? What it the last node before the Telegram sender?

All message nodes (like text, image, audio, etc) that are supposed to be connected to the Telegram sender have a line like this:

var chatId = msg.payload.chatId || (originalMessage && originalMessage.chat.id);

that takes the chatId from the payload or from the originalMessage.
That approach is working for a flow like this

https://github.com/guidone/node-red-contrib-chatbot#send-image

Here the http node is preserving the msg.originalMessage and the image node creates the payload using the id of the originalMessage.

This works as long as you use e message node (like text, image, audio, etc) to prepare the payload for the sender. You cannot go to the sender directly.
There's no message node for plain file (but I'm planning to create one), what node are you using before the Telegram sender?

from node-red-contrib-chatbot.

Hi.

You are correct, of course.
It is my mistake I wasn't using the 'Message' node before the 'Sender' and that's what caused the issue.

Thanks again!

from node-red-contrib-chatbot.

Thanks for your feedback, perhaps I'll include some detailed error message
in case the flow is going directly to the sender without passing through a
message node.

Guido
Il giorno sab 1 ott 2016 alle 20:00 cowchimp [email protected] ha
scritto:

Closed #22 #22
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#22 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAeq93cWtRF0Em0397yAAh-K6K20YJ3rks5qvp_BgaJpZM4KLveD
.

from node-red-contrib-chatbot.