To receive Open Fire’s Telegram stock briefings, start the bot shown in the app, save your numeric Chat ID, test delivery and select briefing days in Alert Notification Settings. The current backend schedules the risk-and-alert briefing at 23:00 Europe/Brussels on selected days; it is not a real-time feed of every threshold crossing.

We make Open Fire. These notifications support review, not investment advice or automatic trade execution. Configuration was checked against current app source on 6 November 2026; delivery also depends on the running service.

Inspect the active alert first

Open active alerts from the dashboard. Read the symbol, condition and relevant date, then inspect the underlying holding. An alert is a reason to investigate, not a buy or sell instruction. No alert does not mean no risk.

Configure your own Telegram destination

  1. Open active alerts, then Alert Notification Settings.
  2. Choose Configure Telegram Alerts to open Telegram Configuration.
  3. Start the bot named in that dialog in Telegram. A bot generally cannot initiate a private conversation before you start it.
  4. Follow the current in-app instructions to obtain your numeric Chat ID, enter it and Save. A username is not the numeric ID.
  5. Press Test, then check Telegram itself, not just the app’s confirmation.

Do not publish your real Chat ID or any bot token in a screenshot. Only configure a destination you control. The dialog currently points to a third-party ID helper; do not share private messages or secrets with such a helper.

Choose briefing days deliberately

Choose days in Alert Notification Settings, outside the Telegram destination dialog, and Save. The current scheduled risk-and-alert briefing runs at 23:00 Europe/Brussels on selected days. This timezone follows Brussels daylight-saving changes; it is not a fixed UTC hour.

DCA reminders are separate: their Telegram enable control and selected days govern the current 16:00 Europe/Brussels job. Merely connecting Telegram does not enable every reminder. The server must have Telegram configured and enabled for delivery to happen.

Check delivery as part of setup

The app’s Test action sends the text “OpenFIRE Telegram test.” to the configured destination. In the repository’s isolated UI test, the simulated API returns sent = true and the interface displays “Telegram test sent.” That is a tested UI confirmation, not proof that an actual Telegram message was delivered. We did not send a real notification to a personal account for this article.

For your own setup, press Test and confirm that a message really appears in your Telegram conversation. Only then check the next selected briefing day. A successful immediate test does not prove the scheduled job has run.

Reduce messages that do not help

  • No test message: start the correct bot, check the numeric ID and unblock the bot if needed.
  • Test works but no briefing: check the selected day and 23:00 Brussels time, saved settings and server Telegram availability.
  • DCA reminder missing: check its separate enable control and reminder days.
  • Unexpected or repeated information: inspect the data date and configured conditions before acting.

The backend handles missing chat IDs, blocked bots and disabled Telegram configuration as delivery failures. Contact support with the time and visible error, not a bot token. Telegram’s bot FAQ explains the platform’s bot model.

Compare the notification with the dashboard before making any financial decision. A stale, delayed or missing message should never be your only risk check.