appleboy/telegram-action

Add support for sending messages to Topics

faizanakram99 opened this issue ยท 17 comments

Messages can be send to topics by reply_to_message_id parameter (with the message id with which topic was created)

upvote this feature too.

+1

+1

+1

This feature is really needed ๐Ÿ‘

+1
Are there any updates, forks, or alternatives?

+1 Are there any updates, forks, or alternatives?

@MarkParker5, you can use Telegram's API.

+1 Are there any updates, forks, or alternatives?

@MarkParker5, you can use Telegram's API.

Already. There is an example:

jobs:
  send_message:
    runs-on: ubuntu-latest
    steps:
    - name: Send Telegram Message
      run: |
        msg_text='Your message text here'
        curl -s -X POST 'https://api.telegram.org/bot${{ secrets.TOKEN }}/sendMessage' \
        -d "chat_id=${{ secrets.CHAT_ID }}&text=${msg_text}&reply_to_message_id=${{ secrets.MSG_ID }}"

+1

+1 Are there any updates, forks, or alternatives?

@MarkParker5, you can use Telegram's API.

Already. There is an example:

jobs:
  send_message:
    runs-on: ubuntu-latest
    steps:
    - name: Send Telegram Message
      run: |
        msg_text='Your message text here'
        curl -s -X POST 'https://api.telegram.org/bot${{ secrets.TOKEN }}/sendMessage' \
        -d "chat_id=${{ secrets.CHAT_ID }}&text=${msg_text}&reply_to_message_id=${{ secrets.MSG_ID }}"

Yeah then what is the point of using this action?

Yeah then what is the point of using this action?

Action is more convenient, but given that it does not support the required functionality at least now, we have to use the API directly. My example isn't the answer to your issue (I actually support it and would like to have this feature), but the answer for developers who faced the same problem and need a workaround right now.

Yeah then what is the point of using this action?

Action is more convenient, but given that it does not support the required functionality at least now, we have to use the API directly. My example isn't the answer to your issue (I actually support it and would like to have this feature), but the answer for developers who faced the same problem and need a workaround right now.

ah ok, thanks for clarifying. Yes indeed, we also used the underlying api then