How to trigger telegram command?
up vote
0
down vote
favorite
How can I trigger the telegram /myCustomCommand
- command using curl?
Currently the message /myCustomCommand gets logged into my chat but obviously telegram is interpreting this text as message instead of a command so nothing happens.
This is my script:
#!/bin/bash
TOKEN="xyz"
CHAT_ID="123"
MESSAGE="/myCustomCommand"
URL="https://api.telegram.org/bot$TOKEN/sendMessage"
curl -s -X POST $URL
-d chat_id=$CHAT_ID
-d text="$MESSAGE"
bot.command("myCustomCommand", (ctx)=>{
// will not be triggered
})
How can I fix this? Any help would be really appreciated.
javascript bash curl bots telegram
add a comment |
up vote
0
down vote
favorite
How can I trigger the telegram /myCustomCommand
- command using curl?
Currently the message /myCustomCommand gets logged into my chat but obviously telegram is interpreting this text as message instead of a command so nothing happens.
This is my script:
#!/bin/bash
TOKEN="xyz"
CHAT_ID="123"
MESSAGE="/myCustomCommand"
URL="https://api.telegram.org/bot$TOKEN/sendMessage"
curl -s -X POST $URL
-d chat_id=$CHAT_ID
-d text="$MESSAGE"
bot.command("myCustomCommand", (ctx)=>{
// will not be triggered
})
How can I fix this? Any help would be really appreciated.
javascript bash curl bots telegram
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
How can I trigger the telegram /myCustomCommand
- command using curl?
Currently the message /myCustomCommand gets logged into my chat but obviously telegram is interpreting this text as message instead of a command so nothing happens.
This is my script:
#!/bin/bash
TOKEN="xyz"
CHAT_ID="123"
MESSAGE="/myCustomCommand"
URL="https://api.telegram.org/bot$TOKEN/sendMessage"
curl -s -X POST $URL
-d chat_id=$CHAT_ID
-d text="$MESSAGE"
bot.command("myCustomCommand", (ctx)=>{
// will not be triggered
})
How can I fix this? Any help would be really appreciated.
javascript bash curl bots telegram
How can I trigger the telegram /myCustomCommand
- command using curl?
Currently the message /myCustomCommand gets logged into my chat but obviously telegram is interpreting this text as message instead of a command so nothing happens.
This is my script:
#!/bin/bash
TOKEN="xyz"
CHAT_ID="123"
MESSAGE="/myCustomCommand"
URL="https://api.telegram.org/bot$TOKEN/sendMessage"
curl -s -X POST $URL
-d chat_id=$CHAT_ID
-d text="$MESSAGE"
bot.command("myCustomCommand", (ctx)=>{
// will not be triggered
})
How can I fix this? Any help would be really appreciated.
javascript bash curl bots telegram
javascript bash curl bots telegram
edited Nov 18 at 16:29
asked Nov 18 at 16:23
jonas00
8671619
8671619
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53363010%2fhow-to-trigger-telegram-command%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown