Support Board
Date/Time: Wed, 12 Aug 2026 09:03:02 +0000
[User Discussion] - Notifier Get Automated Trading System Alerts via Telegram free study
View Count: 19
| [2026-08-12 05:57:53] |
| User263526 - Posts: 2 |
|
I know that many professional developers are skeptical about sending trading signals through Telegram, but I’m not using this for any production-grade trading system. I tested it thoroughly, and it works very fast and reliably. I also tried to cover the main issues related to reliable message delivery. Notifier made for automated trading running on a machine you are not sitting in front of. Your system trades on a VPS or in the next room, and you get a Telegram message every time it does something: order placed, order filled, position opened or closed, connection lost, auto trading switched off. Manual trading is reported exactly the same way, if you want that too. Nothing to set up but a bot token. Put it on the same chart as your trading system. It reads everything on that symbol and account by itself. You change nothing in your trading study, and it places no orders of its own. Install Copy Production_Notifier.cpp into your Sierra Chart ACS_Source folder Analysis → Build Custom Studies DLL → Build → Remote Build Studies → Add Custom Study → Production Notifier One copy per trading chart. Nothing to download and no libraries to install — it is one file and it builds with Remote Build as it is. Telegram Write to @BotFather, send /newbot, copy the token he gives you. Now write any message to your new bot. Bots cannot start a conversation, so without this step nothing works. Open this in a browser with your token in place of <TOKEN>:https://api.telegram.org/bot<TOKEN>/getUpdates Find "chat":{"id":NNNNNNNNN in the text. That number is your Chat ID. It is not the same number as the one inside your token. Put the token and the Chat ID into the study settings and set Enable Telegram Sending to Yes. Use After you add the study the chart shows WAITING FOR TRADE DATA. Wait until it says MONITORING — up to a minute if you are flat, a few seconds if you already have a position or orders. This line means it is ready: 23:48:03 BASELINE: pos 0 @ 0, working orders 0, fills seen 6 [SIM MODE] Start your system after that line. Anything you do before it counts as the starting state instead of arriving as messages. Try it in Trade Simulation Mode first. Simulated trading is reported exactly the same way, and the baseline line ends with [SIM MODE] so you always know which one you are looking at. What you get A bracket entry arrives as one message, not four: 23:17:54 ORDER NEW: #255781 SELL 1 Limit @ 7757.5 (child of #255780) 23:17:54 ORDER NEW: #255782 SELL 1 Stop @ 7752.5 (child of #255780) 23:17:54 FILL: BUY 1 @ 7755 (order #255780, pos now 1) 23:17:54 POSITION OPENED: LONG 1 @ 7755 Orders — placed, canceled, rejected with the reason from the broker. Fills and position — opened, closed with the profit or loss, reversed, resized. Connection — lost, reconnecting, back. Auto trading switched on or off, and Trade Simulation Mode switched on or off. Those last two are the ones that catch people out. Any of them can stop your system dead or quietly send it to the simulator, and Sierra says nothing. Everything also goes into a text log file on disk. That file is written first and does not depend on Telegram in any way. The path is printed to the Message Log at startup. If Telegram is unavailable the messages wait and go out when it comes back. A long outage eventually drops the oldest ones, and the next message that gets through tells you how many were lost. Limits If Sierra Chart itself dies — crash, freeze, power cut — nothing arrives. The study cannot report its own death. Noticing that silence is a separate job and this study does not do it. If your system tries to place an order and Sierra refuses it before it becomes an order at all — position limit hit, account settings wrong — there is no order, so there is nothing to report. Rejections that come back from the broker do arrive. During a chart replay it stays quiet. Replay trades are not real trades. Your bot token is stored as plain text inside the chartbook file. Whoever gets that file gets your bot. Date Time Of Last Edit: 2026-08-12 06:00:59
|
 Production_Notifier.cpp - Attached On 2026-08-12 05:35:23 UTC - Size: 47.51 KB - 1 views Production_Notifier_64.dll - Attached On 2026-08-12 05:36:02 UTC - Size: 971.5 KB - 0 views  SierraChart_64_4ikgwF4zmN.png / V - Attached On 2026-08-12 05:52:39 UTC - Size: 44.24 KB - 3 views |
To post a message in this thread, you need to log in with your Sierra Chart account: