> For the complete documentation index, see [llms.txt](https://docs.datacake.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datacake.de/portal/rule-engine/new-rule-engine/actions/sending-notifications-via-telegram.md).

# Sending notifications via Telegram

This guide shows you how to send notifications triggered by rules to a Telegram user using the pushmore.io service

While the Datacake Rules Engine does not have a dedicated Telegram action, it is still possible to send notifications thanks the the [Push More](https://pushmore.io/) service from [Marc Köhlbrugge](https://twitter.com/marckohlbrugge).

{% embed url="<https://youtu.be/jiETC-u7OMg>" %}

## Create Rule

First, create your Rule like you normally would under the Rule Engine tab, like the following:

<figure><img src="https://2221155863-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LNA8_b8wmabHgJ0QXoJ%2Fuploads%2FV4qqCAAGU25v3HybCYBD%2FScreenshot%202026-10-21%20at%2015.19.38.png?alt=media&amp;token=45736f7d-e2b5-48dd-a663-759b5852a9b3" alt=""><figcaption></figcaption></figure>

## Create Telegram Action

Go to <https://pushmore.io/> and click the "Add to Telegram" button. This will send a `/start` message to their bot, which will respond with a unique URL (something in the format of <https://pushmore.io/webhook/uniqueID>).

Navigate to the Configure Action part of your Rule and click "Add Action", then select Webhook. Under Description, provide something intuitive such as "Telegram Notification".\
\
For the Webhook URL, paste the unique URL that was sent to you earlier on Telegram for Pushmore.IO.\
\
Remove any unnecessary Headers for the payload.

The "Payload" is the message that will be sent, so you can clear it, type your own message and optionally insert placeholders, for example like this:

<figure><img src="https://2221155863-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LNA8_b8wmabHgJ0QXoJ%2Fuploads%2FHulaeXVJXd0T4ynrvZgs%2FScreenshot%202026-10-22%20at%2015.21.11.png?alt=media&amp;token=fcc910b6-ecd3-4eec-a853-563114548506" alt=""><figcaption></figcaption></figure>

You can then select "Update Action" and don't forget to Save your Rule at the bottom of the screen!\
\
Once the conditions are met, you should receive a message like the following:

<figure><img src="https://2221155863-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LNA8_b8wmabHgJ0QXoJ%2Fuploads%2F3rZQZQq9mIJ00BFyTzfl%2FScreenshot%202026-10-22%20at%2015.37.25.png?alt=media&amp;token=663f61fe-a505-42ea-bf2b-e7c176243a28" alt=""><figcaption></figcaption></figure>

You're all set to receive notifications now on Telegram 🚀


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.datacake.de/portal/rule-engine/new-rule-engine/actions/sending-notifications-via-telegram.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
