Telegram Notifications

[robi]

How do notifications via Telegram work?

I have them set up easily with a tgram:// URI, but whatever I put into the Notifiers screen for Telegram, I get a 404 when testing it.

[jypelle]

Hi robi

You have to create a telegram bot and retrieve its API Token and ChatID.

[robi]

@jypelle I already have as noted in my question, the issue is the documentation doesn't show an example of how to use that information and input it into your form.

It might be a nice update if you accept a tgram URI like Discord accepts a URL, so humans don't have to parse out which numbers are which. Also the incrementing input fields here doesn't make sense, especially starting from 0.

Would you make it easier on us please?

FYI for everyone else, this is what the tgram:// URI looks like:
tgram://1234567890:AABjz5PVuBo0rRKQqRg9PjKRHYk14VTtzDU:123456789

The API token field expects the first TWO fields:
1234567890:AABjz5PVuBo0rRKQqRg9PjKRHYk14VTtzDU

The Chat ID field expects the rest:
123456789

[jypelle]

Sorry @robi, I didn't know about the tgram URI syntax. I'll try to take it into account in a future release.

[robi]

@jypelle I just explained it.

It may be AppRise specific:

• Use AppRise URLs for notification to just about any service! Please read the notification services wiki here for important configuration notes.
• discord:// (or https://discord.com/api/webhooks...)) only supports a maximum 2,000 characters of notification text, including the title.
• tgram:// bots can't send messages to other bots, so you should specify chat ID of non-bot user.
• tgram:// only supports very limited HTML and can fail when extra tags are sent, read more here (or use plaintext/markdown format)
• gets://, posts://, puts://, deletes:// for direct API calls (or omit the "s" for non-SSL ie get://) more help here
• Accepts the {{token}} placeholders listed below

[jypelle]

@robi What a pity AppRise doesn't offer its library in Go

At the time I thought tgram URI syntax was a format proposed by Telegram.

In retrospect, I'm a little annoyed at using the format specific to a library.

[robi]

@jypelle I understand. This is what changedetection.io uses. Parse both?

Maybe you can make it even better and come up with your own URI scheme that makes more sense.