TradeJournal Pro can monitor authorized Discord text channels through a bot you create and control. It does not log in as your personal Discord account, and the native route does not promise image or screenshot recognition.
This guide explains the current production workflow, its plan requirements, and the limitations to test before enabling automatic execution.
What the native Discord integration does
The standard Discord Copier uses the Discord REST API and a user-created Discord bot:
- You create a Discord application and bot.
- You invite the bot to a server where you have permission to automate messages.
- You give it read access to the exact text channel you want to monitor.
- TradeJournal Pro polls that channel approximately once per minute.
- New text messages are parsed and recorded.
- The signal waits for review or is routed to an eligible destination, depending on your configuration.
This is scheduled polling—not a permanent WebSocket connection—so allow up to one polling cycle before treating a test as missing.
Step 1 — Create a Discord bot
Open the Discord Developer Portal, create an application, add a bot, and generate its token. Treat the token like a password. Never share it in a public channel or support message. If it is exposed, reset it in Discord before reconnecting.
Invite the bot to the server and give it read access only to the channels required for your workflow. The bot must be able to see the selected channel and its message history.
Step 2 — Connect the bot in TradeJournal Pro
Open Discord Copier, paste the bot token, and test the connection. After the connection succeeds, choose the server and text channel to monitor.
Connecting the bot does not give TradeJournal Pro access to every server your personal Discord account can see. The bot can read only the servers and channels to which it was invited and granted access.
Step 3 — Select a destination and controls
Choose an eligible destination:
- EA account — the signal is queued for an online MT4/MT5 EA receiver.
- Cloud account — eligible Cloud execution can be dispatched after collection and parsing.
- Exchange account — eligible Pro or Lifetime configurations can route supported signals to Binance or Bybit.
Desktop-only execution accounts are not currently selectable as Discord destinations.
Configure fixed sizing or the available risk controls, permitted take-profit levels, playbook, and execution mode. Begin with auto-execution off so you can inspect the parsed result before any broker request.
Step 4 — Use a plain-text test signal
The native polling path reads message text. For the first test, use a clear structure such as:
BUY EURUSD
ENTRY 1.0850
SL 1.0800
TP1 1.0900
TP2 1.0950
The parser extracts supported fields from the text. If the initial parse is incomplete or low confidence, the system can use its AI fallback. That fallback does not change the source limitation: attachment-only, screenshot-only, and embed-only messages are not parsed by the native polling path.
Messages authored by bots are skipped by native polling to reduce automation loops.
Step 5 — Prove the complete demo lifecycle
After sending the test message:
- Allow approximately one minute for collection.
- Confirm that a signal record appears.
- Check the parsed symbol, direction, entry, stop-loss, and targets.
- Approve it manually while testing.
- Confirm the broker accepted the order on a demo account.
- Test the management commands your chosen execution route supports.
A parsed signal is not proof of a broker fill. Broker symbol naming, market hours, minimum size, account mode, margin, and route-specific limits can still reject the order.
Native polling versus the developer webhook
TradeJournal Pro also exposes an authenticated Discord webhook endpoint for developers operating a trusted relay. The relay can send message content and embed text using an EA token or user API token.
That is a separate integration path. The standard Discord Copier screen does not ask you to paste a Discord channel webhook URL. Build a relay only if you control the source, understand token handling, and can validate and monitor every payload.
Plan requirements
Native Discord monitoring requires a Starter, Pro, or Lifetime plan. Exchange routing requires an eligible Pro or Lifetime configuration. Check the current pricing page because plan limits can change.
Current limitations
- Scheduled collection is approximately once per minute, not guaranteed instant intake.
- Native polling reads message text; it does not parse screenshots, attachments, or embed-only messages.
- Bot-authored messages are ignored by native polling.
- Desktop-only execution destinations are excluded.
- The Discord bot must have permission to read the exact channel.
- Broker acceptance and fills depend on the selected route, account, symbol, and market conditions.
Compare the current execution routes on the integrations page, review the compatibility matrix, and open the public Discord Signal Copier page before configuring a live account.
Use only sources you are authorized to automate. Not financial advice. Trading carries risk.