You can easily use the webhook type.
Example:

• target url: https://api.telegram.org/botYOUR_BOT_ID/sendMessage
• HTTP Headers: { "Content-Type": "application/json" }
• HTTP Method: POST
• Customize messages… turn on
• Success message body (or start/error):

{
    "chat_id": "YOUR_CHAT_ID",
    "text": "success - \"{{ job_friendly_name }}\""
}

You can easily use the webhook type. Example:

* target url: `https://api.telegram.org/botYOUR_BOT_ID/sendMessage`

* HTTP Headers: `{ "Content-Type": "application/json" }`

* HTTP Method: POST

* Customize messages… **turn on**

* Success message body (or start/error):

{
    "chat_id": "YOUR_CHAT_ID",
    "text": "success - \"{{ job_friendly_name }}\""
}

Hi @Colonizator1 does this still work ? i've tried without success

@souovan Hi, we are using such telegram notifications right now. Any errors? Did you check your request manually, with postman, for example?

Is there a way to debbug this on AWX ? i only got this when i test the notification

If you are sure that your request URL and data are correct, try to attache notification to some simple template.
I guess you tried to test the notification with the Test button. I failed with it too. But it works well for templates.

Yeah, i've tried with the Test button, i will try attaching on some template.

Any news on this?

@LeoSpyke it's working as webhook type, read my message above

it works strange
I can not edit text message, it does not save it.

@LeoSpyke it's working as webhook type, read my message above

Yes I've seen your message, but I mean that this is not an integration, rather it is a "collateral" workaround that works.
Another native approach would allow to write the token in a specific password field, like the Token for Twilio or Pagerduty, rather than in plain text in the Target URL field.