There is no url or file_id in the response for me to further process the image programmatically, please help.
Hey @Joel1 hope all is good.
You really need to assume that only you know about the problem you are describing and provide more details/context. What nodes are you using? You mentioned “uploaded with telegram” but then show the form trigger node? Please elaborate on your issue and show your workflow.
Hey @jabbson , the node is Telegram’s “Send message and wait for response” with a custom form response type and an image file as a form element (In the 2nd and 3rd image I sent).
The 1st image is the screen displayed when user clicks respond and is prompted to upload the file, this is the same node.
in the 2nd and 3rd image the response from the uploaded file includes the filename and other info relevant to the uploaded file.
My question is how do I process this image further? There is no file_id/url/anything I can use besides the download/view button in the UI.
hello @Joel1
Actually, this makes sense..
This is a form created and uploaded files on your n8n side, not Telegram, so you won’t get any file_id/url/anything from Telegram. Instead, you only get the file binary, which you can use in the next nodes directly or upload somewhere else, since it’s not uploaded to Telegram as I mentioned.
Hello, I understand now. I wish the binary was a separate and clear object when you get the response.
I used the “Extract from file node” with “move file to base64 string” to send it to my server.
Thanks for the help.
1 Like
I see what you mean, thank you for explaining.
When you upload the file through the form, you get a binary in n8n (what you see on your last screenshot). Then you can either process binary by its binary property name (in my case below - Upload) or you can send it back to telegram the same way - through the binary property name.
Let me know if this helps.
No worries! The important thing is that you now understand the logic of the form in (Send and wait for response), it’s not part of Telegram, and that was what caused the confusion.
The next step should be straightforward: either save the file directly in the n8n instance or upload it somewhere else like Google Drive, depending on what your workflow logic..
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.