> For the complete documentation index, see [llms.txt](https://docs.dextrabot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dextrabot.com/features/telegram-alerts-copy-trade.md).

# Telegram Alerts-My Activites

Telegram Alerts for your copy traded wallets.

### 🔔 **How Copy Trade Alerts Work**

Whenever a copied trade executes, Dextrabot sends an **instant Telegram notification** with detailed trade information. This helps users stay aware of their trading activity and react promptly if necessary.

<figure><img src="https://3477217969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaWiG6XtemfC9IwxonZpa%2Fuploads%2FwGwTzqTQVsEoiNQ0pMYx%2Fimage.png?alt=media&amp;token=3b2932f5-5432-4e4c-a80d-afef1bdae6c7" alt=""><figcaption></figcaption></figure>

#### ✅ **Key Trade Alerts:**

1️⃣ **Open Position Alert** – When a new copy trade is successfully opened.&#x20;

2️⃣ **Increase Position Alert** – When the copied trader increases their position.&#x20;

3️⃣ **Decrease Position Alert** – When the copied trader reduces their position.&#x20;

4️⃣ **Change Direction Alert** – When the copied trader flips from long to short or vice versa.&#x20;

5️⃣ **Close Position Alert** – When a copy trade is fully closed.

***

### 📜 **Example Telegram Alert Format**

🔴 **COPY TRADE ALERT** 🔴

🔹 **Coin**: BTC\
🔹 **Price**: $84,430.0\
🔹 **Leverage**: 20x\
🔹 **Action**: 🚀 **OPEN LONG**

#### **🔄 Source Wallet Action**

🔹 **Wallet**: 0x3e...806f (Trader)\
🔹 **Size**: 5.0

#### **👤 Follower Wallet Action**

🔹 **Wallet**: 0x87a...9382 (Follower)\
🔹 **Position Size**: +0.0237\
🔹 **Position Value**: $0.0\
🔹 **Position Margin**: $100.0

✅ **Trade Status**: Successfully copied ⏰ **Time**: 2025-03-15 04:55:52 (GMT)

***

### 🔗 **How to Enable Copy Trade Telegram Alerts?**

To receive real-time notifications, follow these steps:

1️⃣ **Go to your Dextrabot dashboard.**&#x20;

2️⃣ **Navigate to the "Telegram Alerts" section.**&#x20;

3️⃣ **Connect your Telegram account by clicking the authorization link.**&#x20;

4️⃣ **Enable "Copy Trade Alerts."**&#x20;

5️⃣ **You're all set!** Receive instant trade updates directly on Telegram.

🔹 **Pro Tip**: Keep notifications ON to stay updated on market movements and trade adjustments in real time!

***

### 📢 **Why Use Telegram Alerts for Copy Trading?**

✅ **Real-time execution updates** – Get notified instantly when trades are copied.&#x20;

✅ **Full transparency** – Track each trade with detailed insights.&#x20;

✅ **Quick decision-making** – Adjust your strategy based on real-time alerts.

&#x20;✅ **Hands-free monitoring** – No need to stay glued to your screen.

📩 **Start receiving copy trade alerts now and stay ahead of the market with Dextrabot!** 🚀


---

# 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.dextrabot.com/features/telegram-alerts-copy-trade.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.
