Skip to content

notify 0.1.6: a Telegram channel's threadId posts into one topic of a forum group - #1373

Open
garyhedgeme wants to merge 1 commit into
magpie-community:mainfrom
garyhedgeme:notify-telegram-topic
Open

garyhedgeme wants to merge 1 commit into
magpie-community:mainfrom
garyhedgeme:notify-telegram-topic

Conversation

@garyhedgeme

Copy link
Copy Markdown

Telegram's sendMessage reaches one topic of a forum group through message_thread_id; without it, every alert lands in the group's General topic. This adds an optional threadId to the Telegram channel.

  • channels.mjs: threadId (a number or a numeric string) goes out as message_thread_id; an empty or missing one sends nothing extra, so existing channels behave as before.
  • page/app.js: the channel form shows it as Topic ID, not required.
  • README.md: the example carries it, and the options paragraph says where to find the id (the number after the group in a t.me/c/<group>/<topic> link).
  • notify.test.mjs: no message_thread_id without threadId; a number and a numeric string both go out as a number.
  • Version 0.1.5 → 0.1.6.

bun test in packages/notify: 78 pass, 0 fail. We have run this patch against a real forum group: the alert arrived in the topic.

🤖 Generated with Claude Code

… forum group

Telegram's sendMessage takes message_thread_id to reach a topic of a forum group; without it every alert lands in the group's General topic. The channel takes an optional threadId (number or numeric string), the page shows it as Topic ID, and the README says where to find it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant