@alessandromatera/node-red-telegram-api 0.1.0

Node-RED palette for Telegram user-account automation over MTProto.

npm install @alessandromatera/node-red-telegram-api

@alessandromatera/node-red-telegram-api

Node-RED palette for driving a real Telegram user account over MTProto with GramJS, rather than the Telegram Bot API.

What it includes

• telegram-api-config: stores api_id, api_hash, phone number, reconnect settings, and the encrypted session string
• telegram-api-in: emits incoming messages as normalized Node-RED messages, optionally ignoring outgoing/self live events
• telegram-api-send: sends text or media to a peer
• telegram-api-history: fetches recent messages for a peer, optionally only unread incoming messages

Runtime requirements

• Node.js 20+
• Node-RED 4+
• A Telegram API app created at my.telegram.org

Install from npm

cd ~/.node-red
npm install @alessandromatera/node-red-telegram-api

Then restart Node-RED and add the telegram user nodes from the palette.

Install locally for development

npm install
npm run build
cd ~/.node-red
npm install /absolute/path/to/telegram-api

Get your API ID and API hash

Telegram requires your own app credentials for MTProto user-account access.

1. Sign in to Telegram with an official app using the phone number you want to use.
2. Open my.telegram.org and log in with that same phone number.
3. Open API development tools.
4. Fill in the app form with any name, short name, and basic platform details.
5. Save the form and copy the generated api_id and api_hash.

Notes:

• Telegram’s official docs for this flow are here: Creating your Telegram Application.
• Telegram says each phone number can only have one api_id connected to it, so reuse the same credentials for this palette.
• Keep api_hash private. Treat it like a password.

Login flow

1. Open the telegram-api-config node.
2. Enter API ID, API Hash, and your phone number.
3. Click Connect.
4. Enter the login code Telegram sends you.
5. If 2FA is enabled, enter the password.
6. Save and deploy after the session is captured.

The runtime reconnects with the stored session string after restart. If you open an existing config later, Test Connection checks the deployed runtime session. If you need a fresh session, re-enter the API Hash and run Connect again.

Example Node-RED flow

Import this JSON from the Node-RED editor (Menu -> Import -> Clipboard) to get a starter flow with:

• one telegram-api-config node
• one telegram-api-send example that sends to Saved Messages
• one telegram-api-in listener that prints incoming messages
• one telegram-api-history example that reads the last 5 messages from Saved Messages

After importing:

1. Open the My Telegram config node.
2. Enter your API ID, API Hash, and phone number.
3. Click Connect, complete the login flow, then Deploy.
4. Use the inject nodes to test sending and reading history.

[
  {
    "id": "a1f4d7c2e9b00101",
    "type": "tab",
    "label": "Telegram User Example",
    "disabled": false,
    "info": ""
  },
  {
    "id": "b2f4d7c2e9b00102",
    "type": "telegram-api-config",
    "name": "My Telegram",
    "reconnectMinMs": "2000",
    "reconnectMaxMs": "30000",
    "downloadDir": ""
  },
  {
    "id": "c3f4d7c2e9b00103",
    "type": "inject",
    "z": "a1f4d7c2e9b00101",
    "name": "Send test message",
    "props": [
      {
        "p": "payload"
      }
    ],
    "repeat": "",
    "crontab": "",
    "once": false,
    "onceDelay": 0.1,
    "topic": "",
    "payload": "hello from Node-RED",
    "payloadType": "str",
    "x": 170,
    "y": 100,
    "wires": [
      [
        "d4f4d7c2e9b00104"
      ]
    ]
  },
  {
    "id": "d4f4d7c2e9b00104",
    "type": "telegram-api-send",
    "z": "a1f4d7c2e9b00101",
    "name": "Send to Saved Messages",
    "account": "b2f4d7c2e9b00102",
    "peer": "@savedmessages",
    "x": 470,
    "y": 100,
    "wires": [
      [
        "e5f4d7c2e9b00105"
      ]
    ]
  },
  {
    "id": "e5f4d7c2e9b00105",
    "type": "debug",
    "z": "a1f4d7c2e9b00101",
    "name": "Send result",
    "active": true,
    "tosidebar": true,
    "console": false,
    "tostatus": false,
    "complete": "true",
    "targetType": "full",
    "x": 760,
    "y": 100,
    "wires": []
  },
  {
    "id": "f6f4d7c2e9b00106",
    "type": "telegram-api-in",
    "z": "a1f4d7c2e9b00101",
    "name": "Incoming messages",
    "account": "b2f4d7c2e9b00102",
    "includeRaw": false,
    "unreadOnly": false,
    "x": 190,
    "y": 200,
    "wires": [
      [
        "07f4d7c2e9b00107"
      ]
    ]
  },
  {
    "id": "07f4d7c2e9b00107",
    "type": "debug",
    "z": "a1f4d7c2e9b00101",
    "name": "Incoming debug",
    "active": true,
    "tosidebar": true,
    "console": false,
    "tostatus": false,
    "complete": "true",
    "targetType": "full",
    "x": 470,
    "y": 200,
    "wires": []
  },
  {
    "id": "18f4d7c2e9b00108",
    "type": "inject",
    "z": "a1f4d7c2e9b00101",
    "name": "Read last 5",
    "props": [
      {
        "p": "payload"
      }
    ],
    "repeat": "",
    "crontab": "",
    "once": false,
    "onceDelay": 0.1,
    "topic": "",
    "payload": "",
    "payloadType": "date",
    "x": 150,
    "y": 300,
    "wires": [
      [
        "29f4d7c2e9b00109"
      ]
    ]
  },
  {
    "id": "29f4d7c2e9b00109",
    "type": "telegram-api-history",
    "z": "a1f4d7c2e9b00101",
    "name": "Saved Messages History",
    "account": "b2f4d7c2e9b00102",
    "peer": "@savedmessages",
    "limit": "5",
    "includeRaw": false,
    "x": 460,
    "y": 300,
    "wires": [
      [
        "3af4d7c2e9b0010a"
      ]
    ]
  },
  {
    "id": "3af4d7c2e9b0010a",
    "type": "debug",
    "z": "a1f4d7c2e9b00101",
    "name": "History debug",
    "active": true,
    "tosidebar": true,
    "console": false,
    "tostatus": false,
    "complete": "true",
    "targetType": "full",
    "x": 750,
    "y": 300,
    "wires": []
  }
]

You can replace @savedmessages with any username or numeric peer id once the flow is working.

Message contract

Incoming and action nodes use this shape:

• msg.payload: the main payload for the node
• msg.telegram: normalized Telegram metadata

Common metadata fields:

• msg.telegram.peer: { id, type, username, title, ref }
• msg.telegram.chatId
• msg.telegram.senderId
• msg.telegram.messageId
• msg.telegram.media
• msg.telegram.raw when the node is configured with Include Raw

telegram-api-in node options:

• Unread Only: ignores outgoing/self live events and only emits unread incoming live messages
• This is a live event filter only. It does not backfill unread messages that arrived before the node started

Send node input patterns

Text only:

{
  "payload": "hello from Node-RED",
  "telegram": {
    "peer": "@username"
  }
}

Media by local path:

{
  "payload": {
    "caption": "daily report",
    "mediaPath": "/tmp/report.pdf"
  },
  "telegram": {
    "peer": "@username"
  }
}

Media by Buffer:

msg.payload = Buffer.from("...");
msg.telegram = {
  peer: "@username",
  fileName: "image.jpg",
  caption: "generated by a flow"
};
return msg;

History node input supports:

• msg.telegram.peer to override the configured peer
• msg.telegram.limit or msg.limit to control how many messages are returned
• msg.telegram.offsetId or msg.offsetId to paginate older history
• msg.telegram.unreadOnly or msg.unreadOnly to return only unread incoming messages

Current v1 scope

• Incoming messages via NewMessage
• Text and media sends
• Basic history fetch

Not included yet:

• secret chats
• edits/deletes
• contact management
• stories, calls, or generic low-level MTProto requests