Telegram signal setup and troubleshooting

This category covers the current Telegram signal workflow in DaneTrades: connecting the Telegram account, configuring signal detection, testing parsing, handling provider symbol names, and setting up Telegram receiver notifications when you want event messages back into Telegram.

Start here Open Copiers

Built around the current Telegram signal and Telegram receiver modals in `Copiers`
Covers keywords, clean text, symbol aliases, test signal preview, and receiver templates
Designed to reduce missed signals, parse failures, and noisy notification setups

Recommended order

Read these in sequence for a safer Telegram setup

Start here: Telegram Signals. Understand the overall workflow first.
Signals not detected or parse failed. Confirm messages are reaching the app before changing copier behavior.
Keyword presets and clean text. Tune detection without stripping out useful signal content.
Testing before going live. Validate parsing on demo before you enable the connection.
Provider formats and symbol aliases. Adapt unusual provider wording and naming safely.
Multi-TP and entry rules. Decide how Telegram-specific trade logic should behave.
Telegram receiver notifications. Configure outbound Telegram messages only after the core trade flow works.

Articles

Current Telegram signal guides

These guides are aligned to the current Telegram configuration tabs and Telegram receiver notification flow in the app.

Orientation

Start here: Telegram Signals

Understand the order for connecting Telegram, validating parsing, mapping symbols, and going live more carefully.

Read article

Troubleshooting

Signals not detected or parse failed

Fix the two most common Telegram issues first: no signal detection at all, or messages that arrive but cannot be parsed.

Read article

Keywords

Keyword presets and clean text

Use safer detection keywords, ignore rules, and clean-text settings without over-filtering real signals.

Read article

Safety

Testing before going live

Validate parsing, symbol mapping, and copied behavior on a safer path before you enable the live connection.

Read article

Providers

Provider formats and symbol aliases

Adapt common provider wording and use symbol aliases only when Symbol Mapping alone is not enough.

Read article

Trade logic

Multi-TP and Telegram-specific entry rules

Understand how multi-TP, entry zones, pips-from-entry limits, and missing SL or TP rules affect Telegram copying.

Read article

Notifications

Telegram receiver notifications and message templates

Configure outbound Telegram event messages, choose the right event types, and keep templates short and useful.

Read article

Common Questions

Telegram signal FAQ

These are the common Telegram signal questions people usually have before or during setup.

What should I check first if Telegram signals are not detected?

Start with the Telegram account connection, channel access, and Logs. If no signals appear at all, the issue is usually connection state or keyword filtering rather than copier sizing or trade logic.

What does parse failed usually mean on a Telegram signal setup?

It usually means the app received the Telegram message but could not reliably extract the action, symbol, stop loss, or take profit from that message format. The Test Signal preview, keyword rules, clean text settings, and symbol handling are the first places to check.

Should I use Symbol Mapping or symbol aliases first for Telegram providers?

Use Symbol Mapping first. Symbol aliases are the extra layer for cases where provider wording still needs normalization before the mapping can work cleanly.