Discord text → parser → execution route

Copy authorized Discord signals—with the real workflow visible.

Connect a bot you control, select an authorized text channel, inspect the parsed signal, and route it to an eligible EA, Cloud, or exchange destination. Start with review mode and prove the complete lifecycle on demo.

Create account Open Discord Copier

Paid feature · use only servers and channels you are authorized to automate · demo first

Native Discord route

Actual production behavior

Available
AuthenticationYour Discord bot token
InputSelected channel text
CollectionScheduled, about once/minute
DestinationsEligible EA, Cloud, exchange
ControlReview first or auto-execute
Not a personal-account login. Not an image reader. Not a promise of broker fills.

Five-step setup

From a permitted channel to one broker-demo proof

01

Create your Discord bot

Create an application in the Discord Developer Portal, add a bot, and copy its token. Treat that token like a password and rotate it in Discord if it is ever exposed.

02

Give the bot channel access

Invite the bot to a server you control or are authorized to automate. It only needs read access to the exact text channels you intend to monitor.

03

Connect and choose a channel

Open Discord Copier, paste the bot token, test the connection, then choose the server and text channel. TradeJournal Pro does not sign in as your personal Discord account.

04

Choose an eligible destination

Select an EA or Cloud account, or an eligible exchange account. Set sizing, the permitted TP levels, playbook, and whether parsed signals wait for review or auto-execute.

05

Prove it on demo

Send one plain-text signal, allow up to one polling cycle, inspect the parsed record, then confirm the resulting demo order and management lifecycle at the broker.

Supported today

  • Selected Discord server text channels that the connected bot can read
  • Direction, symbol, entry, stop-loss, and supported take-profit extraction from message text
  • Native parser with AI fallback when the first parse is incomplete or low confidence
  • EA queue, eligible Cloud routing, and eligible Binance or Bybit exchange routing
  • Fixed sizing, risk controls, TP selection, playbooks, review-first, and auto-execution modes
  • Signal records and execution evidence inside the TradeJournal Pro workspace

Limits you should know first

  • Native Discord monitoring is scheduled polling, not a permanent Discord WebSocket connection; allow approximately one minute for a new message to be collected.
  • The native polling path reads message text. Attachments, screenshots, and embed-only messages are not parsed by that path.
  • Messages written by bots are skipped by native polling to prevent automation loops.
  • Desktop-only execution accounts are not selectable as Discord destinations today.
  • Discord intake is a paid-plan feature; exchange destinations require an eligible higher plan and configured exchange account.
  • Broker acceptance and fills are never guaranteed. Test the exact symbol, broker, account mode, and command lifecycle on demo.

Advanced webhook relay

A developer-controlled relay can POST message content and embed text to TradeJournal Pro's authenticated Discord webhook endpoint. This is separate from native bot polling and requires an EA or user API token. It is not a webhook URL field in the standard Discord Copier screen.

Read the API reference

Straight answers

Discord copier FAQ

Does TradeJournal Pro log in to my personal Discord account?

No. You create a Discord bot, invite it to a server where you have permission, and grant it access to the specific text channel you want to monitor.

Is Discord copying instant?

The native integration polls on a schedule of approximately once per minute. After collection, eligible Cloud or exchange routes can be dispatched immediately, while EA signals wait in the EA queue for the receiver to collect them.

Can it read screenshots and image-only signals?

Not through the native Discord polling route today. Use a plain-text signal containing the symbol, direction, entry, stop-loss, and targets. Image and attachment parsing must not be assumed.

Can I use a webhook instead of native polling?

Developers can send trusted relay payloads to the authenticated Discord webhook endpoint. That is a separate integration path, not a channel webhook field in the standard Discord Copier screen.

Which plan do I need?

Discord source monitoring requires Starter, Pro, or Lifetime access. Exchange routing requires an eligible Pro or Lifetime setup. Current plan limits are shown on the pricing page.