> For the complete documentation index, see [llms.txt](https://docs.posynt.win/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.posynt.win/guides/notifications.md).

# Discord & Telegram notifications

Get posts straight to where your community lives — no code required. Everything is configured from your **client dashboard**.

## Discord

1. In your Discord server: **Channel settings → Integrations → Webhooks → New webhook**.
2. Copy the **webhook URL**.
3. In your Posynt dashboard: **Notifications → Discord → paste the URL**.
4. Pick the hashtags to route to that channel.

Each post arrives formatted with the author, the text and a clickable link:

```
◈ New post #ledroplive
@0xwhale — cryptowhale
"gm, the mint is live 🔥 #ledroplive"
→ View on X
```

## Telegram

1. Create a bot via [@BotFather](https://t.me/BotFather) and grab its **token**.
2. Get your **chat ID** (via [@userinfobot](https://t.me/userinfobot) or the group ID).
3. In your Posynt dashboard: **Notifications → Telegram → paste token + chat ID**.

{% hint style="info" %}
You can route different hashtags to different channels / chats. For example `#drop` to your public channel and `#alpha` to a private one.
{% endhint %}

## Multiple Discord webhooks

You can add **several Discord webhooks** from the dashboard. Each one can be scoped to specific hashtags/accounts (e.g. one webhook only for `#alpha`, another only for `@officialoddguy`) — leave the sources empty to send everything.

How many you can add is capped by your plan — 1 (Starter), 5 (Pro), 10 (Business); see `webhooks_limit` on `GET /v1/me`. `PUT /notifications` returns `403 plan_limit_reached` if you try to save more than that. Telegram is always a single bot/chat on every plan, so there's nothing to cap there.

## Source filter

Each channel can be routed to **hashtags & accounts**, **hashtags only**, or **accounts only** — so you can send hashtag hits to one channel and account posts to another. Use the **Send test** button to verify a webhook/bot instantly.

## Engagement alerts

If you've turned on [engagement tracking](/api-reference/tracks.md#engagement-tracking) for a hashtag or account, each channel has a separate opt-in checkbox — *"Also alert on new RT/like/comment on engagement-tracked posts"* — for a notification every time a **new** account retweets, likes, or replies to one of those posts (only for whichever of those three you actually turned on for that source — see [Engagement tracking](/api-reference/tracks.md#engagement-tracking)). This is additive and bypasses the hashtags/accounts filter above entirely: leave it off to keep just the original "new post" alerts, since engagement can fire far more often than new posts do.

## Custom messages

Leave the message empty for the default card, or write your own template. For Discord you can also set the **bot name**. Available placeholders:

| Placeholder | Value                                 |
| ----------- | ------------------------------------- |
| `{source}`  | `#hashtag` or `@account` that matched |
| `{author}`  | author's handle (e.g. `@0xwhale`)     |
| `{name}`    | author's display name                 |
| `{text}`    | the post text                         |
| `{url}`     | direct link to the tweet              |
| `{hashtag}` | the hashtag (empty for account posts) |
| `{account}` | the account (empty for hashtag posts) |

Example: `🔥 New from {source}: {text}\n{url}`


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.posynt.win/guides/notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.