Connect an authorized source
Link only a Telegram channel you are allowed to monitor and confirm a test message appears before enabling execution.
Telegram → cTrader
Copy Telegram signals to cTrader—with the beta limits visible
Parse supported entries, stops and targets, apply your own account rules, and route eligible instructions through the local beta cBot. cTrader Cloud is not verified. Every broker and command must pass your demo test first.
Current route status
Native cBotBeta · Limited
Runs in your cTrader instance on a PC or VPS. Each broker lifecycle must be validated on demo.
MetaApi CloudUnavailable · Unverified
No documented provider contract or qualifying demo lifecycle has been verified. Do not purchase Cloud expecting cTrader support.
api2trade is not a cTrader execution route in this integration.
Review the local beta cBot
cTrader must remain online on your PC or VPS. Provider-hosted cTrader Cloud is currently unavailable / unverified.
Map symbols and volume
Match channel labels to the broker's exact cTrader symbols, then respect minimum volume, volume step, and stop-distance rules.
Prove the full lifecycle
On demo, test open, modify SL/TP, partial close, breakeven, cancel pending, and close before live funds.
What the cTrader demo must prove
A parsed message is not an executed trade. Test the broker-visible result and management lifecycle on the exact account you intend to use.
Open guided setupSymbol and volume
Confirm symbol aliases, minimum volume, volume step, contract size, and supported order types.
Stops and targets
Verify stop distance, target allocation, selected TP behavior, and small-volume rounding.
Management commands
Test close, partial close, breakeven, modify SL/TP, cancel pending, and close all.
Execution evidence
Compare received, parsed, dispatched, provider response, and the final cTrader order or position.
Telegram to cTrader questions
Is Telegram to cTrader fully certified?
No. The native cBot is currently a beta route and several capabilities are marked Limited until they are certified across more brokers. The public compatibility matrix shows the tested version, date, and limitation for each command.
Do I need cTrader running on a PC or VPS?
Yes. The native beta cBot requires a running cTrader instance. No verified device-free cTrader Cloud route is currently offered.
Can I use api2trade for cTrader?
No. TradeJournal Pro's Cloud provider integrations are offered for MT4/MT5. cTrader Cloud lacks a verified provider contract and demo lifecycle. The local beta cBot is separate.
Is this the same as cTrader Copy?
No. cTrader Copy mirrors strategies inside cTrader's own ecosystem. This workflow reads supported instructions from a user-authorized Telegram source and routes them through a configured TradeJournal Pro receiver.
Can one cTrader order use several take-profits?
The beta cBot can read selected TP1–TP10 targets, but executable slices depend on total volume, broker minimum volume, and volume step. Very small positions may not support several independent target legs.
Validate the cTrader route before live funds
Use the public compatibility matrix as the current source of truth, then make your own broker-visible demo evidence.