AutoMetaTrade Beta: Telegram Signals to MT5, No VPS Needed

AutoMetaTrade, RedFox’s Telegram-to-MetaTrader 5 workspace, is now live in Beta. It reads the Telegram signal channels you choose, applies the Trading Profile you set for each MT5 account, and runs that workflow in a managed cloud, so you do not rent a VPS or leave a computer running a copier. A useful first evaluation is one demo route: one Telegram source, one MT5 demo account and one applied profile, checked link by link.

RedFox announced the launch in its Auto Forward Messages news channel on November 3, 2026. The product’s terms of service name Công ty TNHH Redfox in Hà Nội, Việt Nam as the operator; Auto-Bot.io publishes this guide. Product details below come from the AutoMetaTrade website, its setup guides and its documentation, checked the same day.

What the launch gives signal followers

If you follow trade ideas in Telegram, the manual loop is familiar: read the message, open MT5, retype the symbol, entry, stop and targets, size the position, then watch for updates. AutoMetaTrade turns that loop into a configured route. The product site and launch post describe:

• AI signal parsing that extracts the symbol, direction, entry, stop loss and take-profit levels from a Telegram message, alongside message rules and symbol mapping for broker-specific names.
• Cloud operation: once your accounts are connected, the automation runs in the cloud while your devices are offline. You can close the browser and come back later to review activity.
• One browser dashboard that adapts to phone, tablet and desktop screens, so you can check accounts and settings from whichever device you have with you.
• Trading Profiles with fixed-lot or balance-based sizing, maximum lot and open-trade limits, symbol and time filters, cooldowns and daily loss limits.
• Trade management including entry zones, layered entries, up to five take-profit targets, breakeven and trailing stops.
• One workspace for multiple MT5 accounts, reusable profiles, live positions and a signal-to-trade history that records processing outcomes, including skipped or rejected actions.

The benefit is more than fewer clicks. You can audit the route through linked records: Signal Log shows the message and its processing outcome, Execution History shows the request and the broker’s fill or rejection, and Positions shows what is open. That trail helps you compare the source, the profile and the account result. AutoMetaTrade does not publish signals or rank channels; you choose the source and its strategy. RedFox is collecting feedback and issue reports in @AutoMetaTradeChat.

How the cloud route fits together

Four pieces make one route. Each has its own readiness state, which is why a green light on one piece does not prove the next.

• Telegram receive source: your personal Telegram account, connected with your phone number and login code, or a bot you add to the channel. Ready when the connection is confirmed and the channel shows Monitoring healthy.
• Channel: links one receive source to zero, one or several MT5 accounts; with no accounts it is monitoring only. Ready when its receiving accounts are saved and each one shows Ready.
• MT5 account: your broker account, connected with its login number, trading password and exact server. Ready when the connection check has finished and the workspace and account controls allow trading.
• Trading Profile: sizing, entries, stops and targets, filters, symbol mapping and management rules. Ready when the saved version shows Applied on that account.

One design choice matters before you build a second route: the Trading Profile belongs to the MT5 account, not to the channel. Changing an account’s profile affects every channel routed to that account. If two sources need different sizing or symbol rules, the execution documentation recommends separate MT5 accounts; the current channel setup has no channel-level trading controls. Sketch your source → account → profile map before you connect anything; it is much easier than untangling a shared profile later.

The current dashboard manages one personal Telegram account per workspace, and that one connection can feed several MT5 accounts. For a channel where you can add a bot, a Telegram bot receive source is the alternative: it verifies reception with a posted check code and processes only posts made after activation.

What to have ready before you connect

• An MT5 demo account. MetaQuotes explains how to open one from the terminal; demo accounts trade virtual money with the same platform functions. When you open it, consider enabling “Use hedge in trading”. AutoMetaTrade requires live accounts to use MT5 hedging mode, so a hedging demo keeps your test closer to a later live setup.
• The account’s terminal credentials: the MT5 login number, the exact broker server name and the trading password. Your broker’s website login is different, and an investor (read-only) password cannot execute trades. Broker support is not universal, so select the exact server in the connection flow; if it is missing, stop rather than pick a similar name.
• Access to one Telegram source that you already understand and are permitted to use, plus the Telegram account that has joined it, or a bot you can add to it.
• A short written rule list: lot or risk sizing, how entries and targets should be handled, and which symbols the source writes versus what your broker calls them.
• A plan check. Each connected MT5 account, demo accounts included, uses a slot in your plan. Plans are paid subscriptions sized by MT5 account capacity and a monthly AI parsing allowance. Review the exact price, included usage, billing period, renewal and cancellation terms at checkout before you agree to pay.

Prove one demo route in six checks

The quick start and RedFox’s demo-first setup guide share one idea: complete a single ready workflow before adding sources or accounts. Here is that path, with what each check actually proves.

1. Connect Telegram and choose one channel. Wait for the connected state, then select the channel by name and username. This proves the account connection; channel monitoring is confirmed separately.
2. Connect the MT5 demo account. Choose Demo Account, enter the login, trading password and exact server, and wait through the connection check. A progress indicator or an accepted request is not readiness; open the account and read its final status.
3. Save and apply a Trading Profile. Saving creates a version but does not apply it. Assign it to the demo account and wait until the account shows your intended version as Applied.
4. Route the channel to the demo account. Under Receiving MT accounts, select the demo account and save. Then check two different states: Monitoring healthy for the channel and Ready for the account.
5. Optionally test execution in Signal Tester. Load a sample, compare the parsed fields with the message in Preview, then use Run demo execution. This can place actual orders on the selected demo account. It tests execution on that account, not Telegram reception or channel routing.
6. Follow one new message end to end. Wait for a fresh post in the source. Find it in Signal Log, open Execution History to see whether the request was filled or rejected, then compare Positions with the MT5 terminal. It is the only check in this list that exercises the whole route, for that message.

Record what you saw: the symbol, side, volume, entry, stop loss and targets, compared with your profile and the broker result. Then repeat the checks for every additional account, because permissions, broker symbol names, margin and applied profile versions can differ even for the same message.

Read each result for what it proves

• A Preview of the parsed signal confirms the fields the system read and the profile that would apply. It places no order.
• Run demo execution in Signal Tester tests execution on the selected demo account with its profile; read the final fill or rejection in Execution History and Positions. It does not show that Telegram messages arrive or route to that account.
• The optional Telegram Bot receiver test is a separate reception test that can send received signal text to the selected demo account, so it can execute rather than just collect. It does not test your main channel route; check the receiver’s own status and requirements.
• Received for processing, accepted or queued confirms the message or request entered processing. It is not a broker-confirmed fill.
• A fill or rejection in Execution History and the MT5 terminal confirms the broker outcome for that request. It does not predict how the next signal will behave.
• Pausing a route can stop eligible future instructions from proceeding. It does not itself close open positions or cancel pending orders.

When an outcome is still checking or uncertain, look at the broker history before trying again. Repeating an action to force a visible success can create the duplicate you were trying to avoid. And keep one distinction close: pausing future execution and closing a position are separate actions with separate results.

Set rules you can explain

The profile options are where the time savings come from, and also where assumptions hide. RedFox’s automation and risk guide flags the settings worth deciding deliberately:

• Per-order risk is not a daily cap. A fixed lot or risk percentage governs one order, and risk-based sizing needs a stop loss. Daily loss limits are a separate setting that pauses new copies once reached.
• Layered entries add up. Several small orders across an entry zone can become meaningful combined exposure. Check whether your sizing applies per order or to the whole position.
• Map symbols to your broker. A source may write GOLD while your account uses a broker-specific symbol. Configure the mapping before copying that instrument.
• Time filters use broker-server time, which can differ from your local clock.
• Stops and price filters are instructions, not guaranteed fills. Gaps, liquidity and broker rules can change the final price.

RedFox’s guide to reading a Telegram signal is worth a pass before you write the profile. It covers entry ranges, edits and cancellations, which are exactly where a parser’s reading and the author’s intent can diverge.

Before you connect a live account

Treat the demo route as your acceptance test. When you consider a live account, three details from the MetaTrader connection guide matter:

• Live accounts must use MT5 hedging mode.
• A newly verified live account can enable trading automatically when its Trading Profile is ready and workspace execution is on. Review the workspace and account execution controls before adding any signal route; you can turn trading off.
• Connecting an account does not choose its channels. Routes are assigned under Receiving MT accounts, so check exactly which channels reach the live account.

Decide in advance how often you will check the account and what you will do if the broker, Telegram or the service is unavailable. Cloud operation removes the need to keep your own machine running; it does not replace monitoring. Trading involves risk, and AutoMetaTrade does not provide signals, investment advice or guaranteed returns.

Frequently asked questions

Does my computer have to stay on?

No. After your accounts are connected, the automation runs in AutoMetaTrade’s managed cloud. You can close the browser and return to the dashboard later.

Can I manage it from my phone?

Yes. The dashboard is a responsive web workspace that adapts to phone, tablet and desktop browsers.

Which trading platform does it connect to?

MetaTrader 5. Select your broker’s exact server during connection; a broker appearing in a list does not prove that a particular account or symbol is ready to trade.

Does a successful Signal Tester run mean my channel works?

No. It checks execution on the selected demo account. Confirm reception and routing by following a new message from the source in Signal Log.

Can I use a bot instead of my personal Telegram account?

For channels where you can add a bot, yes. Bot setup verifies reception with a posted check code, only new posts after activation are processed, and each channel uses one receive source at a time.

Can different sources use different rules?

Rules live in each MT5 account’s Trading Profile, so every channel routed to an account shares that profile. Use separate accounts when sources need independent rule sets.

Start with one demo route

If you want Telegram signals executed on MT5 by rules you can read back, without maintaining a VPS, open AutoMetaTrade, connect one source and one demo account, and follow a single new message from Telegram to the broker result. The demo-first guide walks through the same sequence on RedFox’s site.

RedFox also sells MetaTrader tools such as RedFox Copier Pro through MQL5; the RedFox Trading Suite page lists that range. AutoMetaTrade has its own workspace and subscription. If you already run Copier Pro, our guide to a skipped second trade covers that product’s order limits.