n8n - 💡(How to fix) Fix Telegram Send Photo node reports binary.data missing even though image is successfully sent

Bug Description

Environment

• n8n version: Version
• Telegram node: Send Photo
• AI image generation workflow

Problem

The Telegram node successfully sends the image to the Telegram chat, but the execution is still marked as failed with:

"This operation expects the node's input data to contain a binary file 'data', but none was found [item 0]"

Verified

• chat_id is correct
• image is delivered successfully
• IF node confirms binary.data exists before Telegram node
• binary key is named data
• reproduced across multiple executions
• workflow execution still marked as error

Additional observation

This seems related to binary validation/post-processing after successful upload. <img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/2bfb22f7-5f55-4e47-8d74-58258581c266" />

To Reproduce

Steps to reproduce

1. Create a Telegram Trigger node.

2. Connect it to an AI image generation node that outputs binary image data under the data key.

3. Confirm the image node output contains:

   • binary.data
   • valid image metadata (jpg/png)

4. Configure Telegram node:

   • Chat ID: {{ $node["Telegram Trigger"].json["message"]["chat"]["id"] }}
   • Binary File: Enabled
   • Input Binary Field: data

5. Publish and execute the workflow.

6. Send a message to the Telegram bot.

Actual result

• Image is successfully delivered to Telegram chat.
• Telegram API appears to succeed.
• Workflow execution is still marked as failed.
• Telegram node throws: "This operation expects the node's input data to contain a binary file 'data', but none was found [item 0]"

Expected result

• Execution should complete successfully if the image upload succeeds.
• Node should not report missing binary data after successful delivery.

<img width="1920" height="1080" alt="Image" src="https://github.com/user-attachments/assets/5cb14eb2-7ba7-4850-a88b-b6975c423ba6" />

Expected behavior

Expected behavior

If the image upload succeeds and Telegram API returns success, execution should not be marked failed.

Debug Info

{ "errorMessage": "This operation expects the node's input data to contain a binary file 'data', but none was found [item 0]", "errorDescription": "Make sure that the previous node outputs a binary file", "errorDetails": {}, "n8nDetails": { "nodeName": "Send a photo message", "nodeType": "n8n-nodes-base.telegram", "nodeVersion": 1.2, "resource": "message", "operation": "sendPhoto", "itemIndex": 0, "time": "24/05/2026, 20:46:33", "n8nVersion": "2.20.9 (Self Hosted)", "binaryDataMode": "filesystem", "stackTrace": [ "NodeOperationError: This operation expects the node's input data to contain a binary file 'data', but none was found [item 0]", " at assertBinaryData (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2c2e1f47b69b34bef6f634a13cbf61d9/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/binary-helper-functions.ts:109:10)", " at Object.assertBinaryData (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2c2e1f47b69b34bef6f634a13cbf61d9/node_modules/n8n-core/src/execution-engine/node-execution-context/execute-context.ts:106:21)", " at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/Telegram/Telegram.node.ts:2137:42)", " at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2c2e1f47b69b34bef6f634a13cbf61d9/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1048:32)", " at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2c2e1f47b69b34bef6f634a13cbf61d9/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1239:22)", " at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2c2e1f47b69b34bef6f634a13cbf61d9/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1687:38", " at processTicksAndRejections (node:internal/process/task_queues:104:5)", " at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2c2e1f47b69b34bef6f634a13cbf61d9/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2339:11" ] } }

Operating System

Ubuntu Linux 24.04 LTS

n8n Version

2.20.9

Node.js Version

used Docker n8n image

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted