The idea is:
Expose Telegram Bot API 9.4 button enhancements in n8n’s Telegram node UI:
style(danger/success/primary) to change button coloricon_custom_emoji_idto show a custom emoji icon before button text
My use case:
I build Telegram bots with inline keyboards. I want “styled” buttons (success/danger) and custom emoji icons without building raw reply_markup JSON via HTTP Request nodes.
Why it should be added:
- Telegram officially supports these button features (Bot API 9.4)
- Makes Telegram node UX closer to what advanced bots need
- Avoids manual JSON construction and reduces errors
- Keeps workflows maintainable and readable
Proposed UI/UX:
In Reply Markup → Inline Keyboard (and Reply Keyboard):
- Add optional per-button fields:
- Style: default / danger / success / primary (expression-capable)
- Custom Emoji Icon ID: icon_custom_emoji_id (expression-capable)
- Only include these fields in the API payload if set.
Acceptance criteria:
- Supported across Telegram node operations that accept
reply_markup - Correct serialization to Telegram API structures (
InlineKeyboardButton,KeyboardButton) - Backwards compatible default behavior
- Docs updated
Resources:
- Telegram Bot API docs (InlineKeyboardButton / KeyboardButton:
style,icon_custom_emoji_id)