for forwarding notifications to telegram, currently it's impossible to use POST mode of telegram api, since you cannot define json template for BODY, the task could merely completed only with GET mode of telegram api, just because the query string ‘text’ is same in coincidence.
it'll be usefull improve current webhook tab
config: save/load scheme(profile)
template: for each config, you can define GET/POST mode, api url, params, headers, auth, body (like HTTPie), user can define every field as wanted, draft own json contents
variable: user can use specific variables in template, which are your app title, packagename, notification title, notification content, timestamp...
just a random pic for example (i'm not using this app)
https://f-droid.org/repo/tech.bogomolov.incomingsmsgateway/en-US/phoneScreenshots/2.png
for forwarding notifications to telegram, currently it's impossible to use POST mode of telegram api, since you cannot define json template for BODY, the task could merely completed only with GET mode of telegram api, just because the query string ‘text’ is same in coincidence.
it'll be usefull improve current webhook tab
config: save/load scheme(profile)
template: for each config, you can define GET/POST mode, api url, params, headers, auth, body (like HTTPie), user can define every field as wanted, draft own json contents
variable: user can use specific variables in template, which are your app title, packagename, notification title, notification content, timestamp...
just a random pic for example (i'm not using this app)
https://f-droid.org/repo/tech.bogomolov.incomingsmsgateway/en-US/phoneScreenshots/2.png