A useful Telegram to MT5 automation plan records where messages come from, which accounts receive them and what successful execution should look like. Set those decisions before enabling a source. This guide covers deployment planning and ongoing checks; the installation guide covers the EA's file and permission steps.
Updated 10 October 2026.
Choose one execution route per intended workflow
Cloud + EA connects Telegram on this website while MT5 and the EA stay running on your computer or VPS. Windows/VPS App + EA also needs the Windows Client on that machine. MetaAPI uses a connected cloud account without your own terminal and requires a separately paid MetaAPI subscription.
Document the route used by each receiving account. Check the MT5 compatibility checklist if you are unsure which connection is active. Avoid overlapping copiers or routes that might submit the same trade independently.
Write a source-to-account map
For each Telegram source, record the receiving account, broker server, settings profile and execution method. Confirm that you can access the source in Telegram and that it is selected and saved in the copier.
Separate demo and live destinations clearly. Before testing a source, inspect every account receiving it: a test message routed to several accounts can reach more than the one you are watching.
Define the settings you will verify
- Map provider symbols to the broker's exact instrument names.
- Record lot-sizing rules and how valid stop losses affect risk-based sizing.
- Review entry modes, layers and TP slots, including the total intended exposure.
- Check SL/TP overrides, management-message rules and account filters.
- Document duplicate protection and how intentional re-entry should behave.
Use the MT5 installation guide when connecting an EA route. A successful bridge connection is the start of testing, not its acceptance result.
Set demo acceptance criteria
Use a source you control and representative messages with prices valid at your demo broker. Test a normal entry, a supported pending entry, a repeat post and a management instruction separately. Preview unfamiliar formats before sending them.
For each case, compare the original message with parsed fields, routing outcome and broker-confirmed symbol, direction, volume and protective prices. Confirm the intended order count. Investigate missing or extra orders before allowing that format on a live route. The duplicate-order troubleshooting guide helps separate repeated instructions from intentional layers.
Monitor the route after deployment
Before relying on copying, check the license, source selection, receiving account and recent execution results. For EA routes, confirm a running broker-connected terminal, Algo Trading and a recent bridge heartbeat. Review failed, skipped and waiting results in Logs instead of treating message receipt as successful execution.
After a restart, settings change or provider-format change, repeat a controlled demo check. Inspect existing orders before retrying anything with an uncertain result. Keep a dated record of changed settings and the checks performed so that later differences have a clear starting point.