Arixis Trade Broadcaster

Turn your MetaTrader 5 trading activity into professional, automated notifications.

Arixis Trade Broadcaster is a MetaTrader 5 Expert Advisor designed to monitor trading activity across your account and publish informative messages to external communication platforms.

Whether you trade manually, use Expert Advisors, or manage several strategies, Trade Broadcaster helps you follow trading activity without continuously watching your terminal.

Supported integrations

• Telegram: Send trading notifications to a bot conversation, private group or channel, subject to the appropriate bot permissions.

• Discord: Publish messages directly to a Discord text channel using a webhook.

• WhatsApp Cloud API: Send individual messages through Meta's official business messaging infrastructure, subject to account approval, template rules and applicable fees.

• n8n: Deliver structured JSON events to a webhook for custom workflows, databases and automation systems.

Main features

Account-wide monitoring

Monitor trading activity across the connected MT5 account, not only the symbol of the chart where the EA is installed.

Trade event notifications

Configure messages for:

• New positions and trades.

• Stop Loss and Take Profit changes.

• Partial position closures.

• Full position closures.

• Additional volume on existing positions, including netting-related events.

• Daily trading summaries.

Professional message formatting

Choose the message language, time reference, displayed information and privacy settings.

Privacy controls

Hide trade volume or account identifiers when you do not want to disclose sensitive account details. Monetary results can be displayed independently.

Reliable message delivery

The EA includes a local event queue, retry handling, duplicate-prevention mechanisms and recovery settings for interrupted sessions.

Built-in status panel

Monitor active connections, last detected events, successful deliveries, pending messages and delivery errors directly from the chart.

Read-only operation

Arixis Trade Broadcaster is designed for monitoring and reporting. It does not provide trade entry signals or independently open, modify or close trading positions.

Who is it for?

• Manual traders who want notifications of their trading activity.

• Algorithmic traders monitoring Expert Advisors.

• Traders managing private Telegram or Discord communities.

• Developers integrating MT5 trade events with n8n workflows.

• Account operators who need a convenient activity feed.

Requirements

• MetaTrader 5 desktop terminal.

• Active trading account connection.

• Internet connectivity.

• Configured destination credentials and permissions.

• Required URLs added to MetaTrader 5's WebRequest allowlist.

• Meta WhatsApp Business API access for WhatsApp integration.

Important notes

Telegram and Discord require external accounts and valid destination settings. WhatsApp Cloud API may require approved templates, business verification or additional permissions and can incur messaging charges.

Trade Broadcaster reports activity using the information available from the connected terminal and broker. Delivery depends on platform availability, internet connectivity, configuration and external API restrictions.

Arixis Trade Broadcaster keeps your trading activity visible, organized and connected.

1. Installation

1. Open MetaTrader 5.

2. Select File → Open Data Folder.

3. Open MQL5/Experts.

4. Copy ArixisTradeBroadcaster.ex5 into the folder.

5. Restart MT5 or refresh the Navigator.

6. Locate the EA under Navigator → Expert Advisors.

7. Attach it to one chart.

8. Open the input parameters and configure your preferred notification channels.

The EA is designed to monitor the connected account, not just the chart symbol. Start with one instance per account to avoid duplicate notifications.

MT5 must remain running and connected for real-time delivery.

2. Telegram Setup

Create a Telegram bot

1. Open https://t.me/BotFather.

2. Send /newbot.

3. Choose a display name.

4. Choose an available username ending in bot.

5. Copy the API token supplied by BotFather.

Keep the token private.

Find your Chat ID

1. Open your new bot in Telegram.

2. Press Start.

3. Send a message such as Hello Arixis.

4. Open:

https://api.telegram.org/botYOUR_TOKEN/getUpdates

5. Find the chat.id value in the response.

Example:

{ "ok": true, "result": [ { "message": { "chat": { "id": 123456789, "type": "private" } } } ] }

Use chat.id, not update_id, message_id or an unrelated user ID.

For groups or channels, add the bot to the destination, grant the necessary permissions and obtain the destination's Chat ID.

Configure MT5

In the EA input settings:

• Publish to Telegram: true.

• Bot token: your bot token.

• Chat ID: the destination Chat ID.

Open Tools → Options → Expert Advisors, enable WebRequest permissions and add:

https://api.telegram.org

Save the settings.

Test Telegram

Generate a permitted trade event in an isolated demo account, or wait for an event.

Check the EA panel and verify that the message actually arrives in Telegram.

If getUpdates returns {"ok":true,"result":[]}, send a new message to the bot and refresh the request. Another application or an existing webhook may also consume updates.

3. Discord Setup

Create a webhook

1. Open your Discord server.

2. Select the target text channel.

3. Open Edit Channel → Integrations → Webhooks.

4. Create a new webhook.

5. Name it Arixis Trade Broadcaster.

6. Copy the complete webhook URL.

The URL resembles:

https://discord.com/api/webhooks/WEBHOOK_ID/SECRET_TOKEN

Treat it as a private credential.

Configure the EA

• Publish to Discord: true.

• Channel webhook URL: the complete webhook URL.

• Displayed sender name: your preferred sender name.

Allow Discord requests

Add this origin to the MT5 WebRequest allowlist:

https://discord.com

Do not remove the Telegram origin if Telegram remains enabled.

Verify delivery

Check the EA panel and confirm that the destination channel receives a message after a trade event.

A valid-looking configuration alone does not prove successful delivery.

4. WhatsApp Cloud API Setup

WhatsApp requires Meta's official business messaging infrastructure.

Prepare Meta access

1. Open https://developers.facebook.com/.

2. Create a compatible Meta application.

3. Enable WhatsApp Business Platform.

4. Open the WhatsApp API setup area.

5. Obtain the sender Phone Number ID.

6. Obtain a valid access token.

7. Configure an authorized test recipient.

8. Prepare an approved message template when required.

Meta may provide temporary test credentials and a test sender number.

Configure the EA

• Publish to WhatsApp: true.

• Phone number ID: the sender ID supplied by Meta.

• Access token: a valid Meta token.

• Recipients: authorized international-format destination numbers, usually without +.

• Approved template: the exact approved template name.

• Template language code: the corresponding language, such as en_US.

• Graph API version: a version supported by your integration.

The template structure must match the variables supplied by the EA. The configuration shown for version 1.00 expects a template with one body variable, {{1}}.

Allow WhatsApp API requests

Add:

https://graph.facebook.com

Important limitations

• Temporary tokens can expire.

• Test recipients may be restricted.

• Business-initiated messages can require approved templates.

• Meta may charge for messages.

• This integration targets individual recipients, not unrestricted WhatsApp group broadcasting.

• API acceptance does not necessarily confirm final delivery.

5. n8n Webhook Setup

n8n can receive structured trade events and route them into custom workflows.

Create a workflow

1. Open your n8n instance.

2. Create a workflow.

3. Add a Webhook node.

4. Configure the HTTP method expected by the EA, normally POST.

5. Copy the test webhook URL.

6. Start listening for a test event.

Configure the EA

• Publish to an n8n webhook (structured JSON): true.

• Production webhook URL: your active production webhook URL.

• Optional authentication header name: optional authentication header.

• Optional authentication header value: optional secret value.

Use the appropriate test URL while listening for test requests. Activate the workflow and use its production URL for ongoing delivery.

Allow requests

Add your n8n instance's HTTPS origin to MT5's WebRequest allowlist.

Verify

Trigger a test event and inspect the workflow execution. Check the JSON fields actually received before building downstream automations.

The exact event schema should be confirmed against the installed EA version.

6. Event Configuration

The EA offers configurable notifications for:

• New trades: position openings and new trade activity.

• SL / TP changes: Stop Loss and Take Profit modifications.

• Partial closes: reductions in position volume.

• Full closes: completed position closures.

• Volume added to a position: relevant netting events.

• Daily summary: periodic account activity reporting.

Daily summary hour and minute settings determine the intended report time according to the configured time reference.

7. Trade Filters

The EA can be configured to monitor:

• All trades.

• Manual trades only.

• Expert Advisor trades based on magic number.

• Selected symbols only.

Use the symbol filter and origin settings to avoid publishing unrelated strategies.

8. Message Settings

Available configuration options include:

• Message language.

• Server, local computer or UTC time.

• Show or hide lot sizes.

• Show monetary results.

• Show or mask the account number.

• Show a public trade identifier.

• Show close reasons.

• Add a custom introductory line.

For public communities, consider hiding lot sizes and account identifiers.

9. Delivery and Recovery Settings

Version 1.00 includes settings for:

• Waiting briefly after entry for initial SL/TP updates.

• Grouping rapid consecutive modifications.

• Recovering missed events after restart.

• Limiting the age of recoverable messages.

• Maximum delivery attempts.

• HTTP request timeout.

• Retry behavior after a timeout.

• Publishing already-open positions at startup.

A timeout does not prove that the destination failed to receive the request. Retrying may occasionally produce duplicate notifications.

10. Understanding the Status Panel

The chart panel reports the EA's operational state.

Typical fields include:

• Monitoring: account scope and number of open positions.

• Telegram / Discord / WhatsApp / n8n: channel status.

• Last event: most recently detected trading event.

• Last sent: most recently reported delivery.

• Pending: queued messages awaiting processing.

• Failed: messages with recorded failures.

• Discarded: discarded messages.

• Filtered: events excluded by configuration.

• Last error: latest detected problem.

Common channel states:

• OK: a successful request or delivery response was recorded.

• CONFIG: configuration is incomplete or invalid.

• OFF: the channel is disabled.

• STOPPED: publishing has stopped for that channel.

Pause publishing temporarily suspends publication.

Delete local data can remove local queue or recovery information. Do not use it casually when troubleshooting.

11. Common Errors and Solutions

Telegram: WebRequest not allowed

Cause: MT5 has not authorized the Telegram API origin.

Solution: Add https://api.telegram.org under Tools → Options → Expert Advisors → Allow WebRequest for listed URL.

Telegram: 400 chat not found

Cause: Wrong Chat ID, wrong bot, conversation not started or insufficient destination access.

Solution: Send /start to the correct bot, obtain chat.id from getUpdates, verify the token and check group or channel permissions.

Telegram: 401 Unauthorized

Cause: Invalid or revoked bot token.

Solution: Check the token in BotFather. Revoke and replace it if it has been exposed.

Telegram: result: []

Cause: No pending bot updates.

Solution: Send a fresh message to the bot and refresh getUpdates. Check for competing update consumers or an active webhook.

Discord: WebRequest not allowed

Cause: Discord is missing from the MT5 allowlist.

Solution: Add https://discord.com.

Discord: 404 Not Found

Cause: Invalid, incomplete or deleted webhook.

Solution: Create or copy a valid webhook URL and update the EA.

Discord: 401 or 403

Cause: Invalid authorization or insufficient access.

Solution: Verify the webhook and channel permissions.

HTTP 429 Too Many Requests

Cause: The destination's rate limit was exceeded.

Solution: Reduce message frequency and allow the retry queue to respect API backoff instructions.

WhatsApp: HTTP 400

Possible causes: Incorrect recipient, wrong Phone Number ID, missing template, unsupported language or invalid template variables.

Solution: Inspect Meta's detailed error response and verify every field against the configured business account.

WhatsApp: HTTP 401 or 403

Possible causes: Expired token or missing permissions.

Solution: Check token validity, application permissions and access to the sender number.

n8n: No webhook execution

Possible causes: Incorrect URL, inactive workflow, test listener not running, authentication mismatch or blocked WebRequest.

Solution: Verify the test/production URL, activate the workflow, inspect execution logs and authorize the correct HTTPS origin.

Messages remain pending

Possible causes: Connection problems, API failures, invalid configuration, rate limits or temporary outages.

Solution: Fix the underlying connection issue first, then review the queue and retry status.

Warning: Reconnecting may cause older pending messages to be delivered in a batch.

No trade events detected

Possible causes: Incorrect account, restrictive filters, disabled EA, no qualifying activity or history-reading problems.

Solution: Verify the connected account, active EA state, symbol filters, magic-number settings and MT5 logs.

Duplicate messages

Possible causes: Multiple EA instances, retry after an ambiguous timeout or restart recovery.

Solution: Start with one EA instance per account and inspect retry and recovery settings.

12. Recommended First-Time Test

1. Install the EA on an isolated demo account.

2. Enable Telegram only.

3. Confirm the token, Chat ID and WebRequest origin.

4. Generate a permitted demo trade event.

5. Verify that Telegram receives the notification.

6. Enable Discord and repeat the test.

7. Configure WhatsApp and n8n individually, when needed.

8. Inspect pending, failed and discarded message counts.

9. Restart the terminal and verify that recovery does not produce unexpected duplicates.

10. Confirm that the EA never initiates or modifies trades.

13. Official Resources

• Telegram BotFather: https://t.me/BotFather

• Telegram Bot API: https://core.telegram.org/bots/api

• Discord Webhook API: https://discord.com/developers/docs/resources/webhook

• Meta for Developers: https://developers.facebook.com/

• WhatsApp Business Platform: https://developers.facebook.com/docs/whatsapp/

• n8n Documentation: https://docs.n8n.io/

• MQL5 Documentation: https://www.mql5.com/en/docs

Arixis Trade Broadcaster 1.00 — Monitor your trades. Automate your notifications. Stay connected.