ERROR: source.on is not a function in Telegram (photo with buttons)

[artildo]

When I send a photo message via Telegram, no errors
Once I add a button, I get this error:

NodeApiError: source.on is not a function
    at Object.apiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Telegram/GenericFunctions.js:82:15)
    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Telegram/Telegram.node.js:1674:36)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:652:28)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:592:53

The workflow:

[EmeraldHerald]

Hi @artildo - Sorry to hear you’re running into this!

Does this post from Tom help you out?

Where is the Telegram node json parameters for inline buttons

Hi @n8nNinja, you can still use the “Inline Keyboard” option in n8n. You’ll find it under “Reply Markup” when using the Message → Send Message operation: [image] There are no required JSON parameters for this. This is how it looks in the client app: [image]

[artildo]

@EmeraldHerald This is some other case. I do know how to use inline buttons. The point is that for the Photo message they give error.

[EmeraldHerald]

Hi @artildo - you should be able to send an image by selecting ‘Message’ as the Resource and ‘Send Photo’ as the Operation in the Telegram node. Then in the Photo field, you can either pass a file_id for photos that already exist on the Telegram server or pass an HTTPS URL for Telegram to get a photo from the internet.

Hope that helps! If it doesn’t, we may need some more information about your workflow and what you’re trying to do

[artildo]

@EmeraldHerald Hmm. Looks like a bug. You approach works. But if I send binary data — it doesn’t: See below:

Send URL:

Send Binary

[EmeraldHerald]

Hmmm, maybe @mutedjam or @jon tomorrow when both are back in can help confirm expected behaviour

[MutedJam]

Thanks so much for reporting this @artildo! I’ll add this to our bug tracker for a fix.

[mcnaveen]

Hey @MutedJam
Indeed it’s a bug, I’m able to reproduce it.
Is this being fixed? or I’m happy to raise a PR

[EmeraldHerald]

Hi @mcnaveen - I can confirm that our engineers haven’t started working on this yet, and it’s in the backlog. Feel free to create a PR