Telegram account
SupportedAuthorized channels/groups through the user's Telegram session
Requires: Desktop session or connected website Telegram session
The user must be authorized to access and use the source content.
Check where a route runs, whether your device must stay online, how many targets it handles, and which management actions are actually implemented before you subscribe or trade.
6
Supported
2
Beta
2
Limited
5
Planned
Feature-level evidence
Every cell is explicit. Limited means beta, a smaller target range, provider-dependent behaviour, or incomplete broker reconciliation—not full parity.
| Capability | EA MT4 EA 8.06 | EA MT5 EA 8.06 | Desktop MT5 Desktop 2.8.2 | Cloud MT Web executor | cTrader cBot 2026-08-07 | TradeLocker Adapter 2.11.0 | IBKR Desktop bridge 2.8.2 | Binance / Bybit Exchange executor |
|---|---|---|---|---|---|---|---|---|
| Market orders | Supported Native terminal order submission. | Supported Native terminal order submission. | Supported Submitted through the local MT5 bridge. | Supported MetaApi and api2trade routes. | Limited Available through the beta cBot; certify each broker on demo. | Limited Cloud adapter is beta and provider schemas vary. | Supported Allowlisted US stocks and ETFs through the local Gateway. | Supported Supported futures symbols with a hard USDT cap. |
| Pending orders | Supported Limit and stop entries. | Supported Limit and stop entries. | Limited Bridge support depends on the selected MT5 order flow and broker. | Supported Limit and stop entries. | Limited Beta cBot; broker lifecycle validation is required. | Limited Limit and stop entries through the beta adapter. | Limited Supported stock order flows only; validate order type and session. | Not supported The current exchange route opens market entries only. |
| TP1–TP10 | Supported Up to ten selected broker-order slices. | Supported Up to ten selected broker-order slices. | Limited Desktop bridge currently supports TP1–TP5. | Supported Up to ten selected target slices. | Limited The beta cBot reads TP1–TP10 selections. | Limited TP1–TP10 through a beta provider adapter. | Limited Native bracket slices currently stop at TP5. | Limited Only the first selected available target is submitted. |
| Selected TPs | Supported Per-account TP selection is delivered to the EA. | Supported Per-account TP selection is delivered to the EA. | Supported Selection supported inside the TP1–TP5 range. | Supported Selection is resolved before cloud dispatch. | Limited Available in the beta cBot path. | Limited Available in the beta adapter path. | Supported Selection supported inside the TP1–TP5 range. | Limited Selection resolves to one submitted target. |
| Breakeven trigger | Supported Can trigger after the configured TP milestone. | Supported Can trigger after the configured TP milestone. | Supported Bridge manages the configured TP trigger. | Supported Cloud reconciliation applies the configured trigger. | Limited Local beta behaviour requires broker demo validation. | Limited Command supported; automated trigger remains beta. | Limited Breakeven command is supported; trigger timing requires paper validation. | Not supported Full management automation is not exposed for exchange positions. |
| Trailing trigger | Supported Can start after the configured TP milestone. | Supported Can start after the configured TP milestone. | Supported Bridge manages the configured TP trigger. | Supported Cloud trailing supports the configured trigger. | Limited Local beta behaviour requires broker demo validation. | Not supported The beta adapter does not publish trailing parity yet. | Not supported The current IBKR management set does not publish trailing parity. | Not supported The exchange route does not expose trailing management. |
| Partial close | Supported Percent-based close with broker lot normalization. | Supported Percent-based close with broker lot normalization. | Supported Executed through the local bridge. | Supported Executed through the connected cloud provider. | Limited Beta and broker-volume rules apply. | Limited Supported through the beta shared command executor. | Supported Share quantity is reduced through the local Gateway. | Not supported Not exposed by the current exchange command lifecycle. |
| Modify SL / TP | Supported Move/remove SL and move/remove a selected TP. | Supported Move/remove SL and move/remove a selected TP. | Supported Move/remove SL and move TP through the bridge. | Supported Move/remove SL and move TP through the provider. | Limited Beta cBot; validate modification rules on demo. | Limited Supported through the beta shared command executor. | Supported Move SL and a selected TP for supported bracket orders. | Not supported Entry protection may be sent, but later modification is not exposed. |
| Cancel pending | Supported Cancels matching pending EA orders and queued signals. | Supported Cancels matching pending EA orders and queued signals. | Supported Cancels matching bridge orders or queued signals. | Supported Cancels pending provider orders and queued signals. | Limited Beta cBot; validate broker-specific cancellation. | Limited Supported through the beta shared command executor. | Supported Cancels a matching pending stock order. | Not supported Pending entries are not part of the current exchange route. |
| Broker-confirmed fill | Limited Terminal ticket/execution report is recorded; continuous fill reconciliation is limited. | Limited Terminal ticket/execution report is recorded; continuous fill reconciliation is limited. | Limited Bridge tickets are reported; reconcile final state against the terminal. | Supported Provider reconciliation records broker-side position state. | Limited Beta lifecycle reporting is not certified across brokers. | Limited Beta reconciliation depends on provider status schemas. | Supported Order status, filled quantity and average fill price are reconciled. | Limited Exchange response is recorded without the full shared management lifecycle. |
Verification dates identify the reviewed TradeJournal Pro build. Broker server, account type, symbol rules, market hours and permissions still require a demo test.
Last verification dates identify the code/build review—not a promise about every broker server.
| Route | Markets / runtime | Device | Entries / targets | Management | Verified |
|---|---|---|---|---|---|
MT4 Expert Advisor Supported | Forex/CFDs offered by the connected MT4 broker Your MT4 terminal | PC or VPS with MT4 running | Market, limit, and stop entries Select TP1–TP10; split into broker orders | Close, partial close, breakeven, move/remove SL, move/remove TP, trailing, and queued-signal cancel. A single TP leg is closed in-terminal. Broker symbol names, minimum lots, stops, fills, and hedging/netting rules still apply. | EA 8.06 2026-09-02
|
MT5 Expert Advisor Supported | Forex/CFDs offered by the connected MT5 broker Your MT5 terminal | PC or VPS with MT5 running | Market, limit, and stop entries Select TP1–TP10; split into broker orders | Close, partial close, breakeven, move/remove SL, move/remove TP, trailing, and queued-signal cancel. A single TP leg is closed in-terminal. Netting accounts keep one net position per symbol; validate the full lifecycle on demo. | EA 8.06 2026-09-02
|
cTrader cBot Beta | Forex/CFDs offered by the connected cTrader broker Your cTrader instance | PC or VPS with cTrader running | Signal entries through the native cBot Reads TP1–TP10 selections | Local cBot management; broker-specific open/modify/close behaviour requires demo validation. Published as beta until recurring broker lifecycle canaries cover open, modify, partial close, and close. | Public cBot build 2026-08-07 2026-08-07
|
Desktop + MT5 Bridge Supported | Forex/CFDs offered by the local MT5 broker TradeJournal Pro Desktop and MT5 | Windows PC or VPS must stay running | Local Telegram parsing and website-routed entries Select TP1–TP5 | Close, partial close, breakeven, move/remove SL, move TP, and trailing through the bridge. Desktop is a local execution route, not credential-hosted cloud execution. | Desktop 2.8.2 line 2026-09-03
|
Cloud MT4/MT5/cTrader · MetaApi Supported | Forex/CFDs supported by the connected broker/provider account Provider-hosted cloud account | No trading PC after deployment | Market, limit, and stop entries Select TP1–TP10; multi-order target plan | Close, close a target leg, partial close, breakeven, move/remove SL, move TP, and cloud trailing. Provider, broker, market, and network timing vary. A connected account must pass its own demo test. | Current web executor 2026-08-29
|
Cloud MT4/MT5 · api2trade Supported | Forex/CFDs supported by the connected api2trade account Provider-hosted cloud account | No trading PC after deployment | Market, limit, and stop entries Select TP1–TP10; multi-order target plan | Close, close a target leg, partial close, breakeven, move/remove SL, move TP, and cloud trailing. api2trade is MT4/MT5 only in this integration; cTrader is not routed through this provider. | Current web executor 2026-08-29
|
Cloud TradeLocker Beta | Markets enabled by the connected TradeLocker provider TradeJournal Pro cloud adapter | No local trading terminal after connection | Market, limit, and stop entries Select TP1–TP10; broker orders carry absolute SL/TP | Close, partial close, breakeven, move/remove SL, and move TP. Cloud management reuses the shared command executor. Provider schemas and permissions vary. Keep this route on demo until open, modify, partial close, and reconciliation pass for your account. | Public API adapter 2.11.0 2026-08-29
|
Interactive Brokers · local bridge Supported | Allowlisted US stocks and ETFs Desktop + local Client Portal Gateway | Windows PC or VPS must stay running | Market and supported stock order flows TP1–TP5 native bracket slices | Close symbol/all, cancel pending entry, partial close, breakeven, move SL, and move a selected TP. This is not unattended provider-hosted cloud execution. IBKR login, 2FA, session keepalive, and pacing rules still apply. | Desktop IBKR bridge 2.8.2 2026-09-03
|
Binance Futures Limited | Supported Binance futures symbols TradeJournal Pro exchange executor | No local trading terminal | Market entry with USDT safety cap One selected broker TP; if several are selected, the first available target is used | Entry SL/TP submission is supported; the full EA/Cloud command lifecycle is not yet exposed for exchange positions. Not feature-parity with MT4/MT5 Cloud management. | Current exchange executor 2026-08-29
|
Bybit Futures Limited | Supported Bybit perpetual symbols/account types TradeJournal Pro exchange executor | No local trading terminal | Market entry with USDT safety cap One selected broker TP; if several are selected, the first available target is used | Entry SL/TP submission is supported; the full EA/Cloud command lifecycle is not yet exposed for exchange positions. Not feature-parity with MT4/MT5 Cloud management. | Current exchange executor 2026-08-29
|
DXtrade Planned | Not connected No production route | Not applicable | Not supported Not supported | Not supported Do not purchase a plan expecting this route until its status changes to beta or supported. | Not available 2026-08-29
|
MatchTrader Planned | Not connected No production route | Not applicable | Not supported Not supported | Not supported Do not purchase a plan expecting this route until its status changes to beta or supported. | Not available 2026-08-29
|
NinjaTrader Planned | Not connected No production route | Not applicable | Not supported Not supported | Not supported Do not purchase a plan expecting this route until its status changes to beta or supported. | Not available 2026-08-29
|
Tradovate Planned | Not connected No production route | Not applicable | Not supported Not supported | Not supported Do not purchase a plan expecting this route until its status changes to beta or supported. | Not available 2026-08-29
|
ProjectX Planned | Not connected No production route | Not applicable | Not supported Not supported | Not supported Do not purchase a plan expecting this route until its status changes to beta or supported. | Not available 2026-08-29
|
A source is not an execution route. It supplies a message; the selected account route decides where an eligible order is submitted.
Authorized channels/groups through the user's Telegram session
Requires: Desktop session or connected website Telegram session
The user must be authorized to access and use the source content.
Push webhook for bot-visible chats and support notifications
Requires: Bot added where Telegram permits it
Bots cannot read chats they cannot access.
Native polling or incoming webhook
Requires: Authorized server/channel or webhook
Delivery method and plan limits vary.
Authenticated webhook
Requires: Webhook-capable TradingView alert
The alert payload must identify a valid action and symbol.
Authenticated JSON POST
Requires: API/webhook token
Caller retries must preserve a stable identity to avoid duplicates.
Mailbox listener
Requires: Dedicated compatible mailbox configuration
Polling latency and provider security settings vary.
Meta Cloud API webhook
Requires: Meta Business app, approved number, and webhook configuration
Personal WhatsApp chat scraping is not offered.
One parsed source signal can broadcast to several configured accounts with per-account sizing overrides. The separate MT4/MT5 master→follower beta mirrors market and pending entries, pending entry edits/cancels/fills, closes, proportional partial closes, and opt-in later SL/TP edits to exact follower tickets with hard lot caps. Existing-position startup sync is separately opt-in.