A signal written for a forex broker says 'BUY GOLD 0.35 lots'. A futures account has no lots, no GOLD, and no fractional contracts. Three translations have to happen before that message becomes a position, and each one can quietly change the trade.
A signal lands in a Telegram channel at 09:32. It says: BUY GOLD, entry 3,412, stop 3,396, TP1 3,428, TP2 3,450, risk 0.35 lots. On a MetaTrader account that message is almost self-executing. On a Tradovate futures account, not one field in it is directly usable. There is no instrument called GOLD. There is no such thing as 0.35 of a contract. And the price 3,412 is not the price the futures contract is trading at.
Yes, you can copy a Telegram or Discord signal to a futures account, and the setup is not exotic. What it requires is three translations, done in the right order: the instrument has to become a specific contract, the size has to become a whole number of contracts, and the stop and target have to survive the fact that the two markets do not quote the same price. Get any of the three wrong and the trade still executes — just not the trade you were sent.
INFO
Quick answer. A futures account needs a contract mapping rule, whole-number sizing and a rule for what happens to the stop and target. A rule like GOLD=MGC turns the signal's instrument into the front-month micro gold contract; sizing rounds down to whole contracts; and where the provider is a CFD or forex account, the stop and target stay with the provider by default and the futures copy follows the provider's close rather than trying to mirror a price that does not exist on its side.
Tradovate's own support documentation states that prop-firm and evaluation accounts are not eligible for its API, and that a funded live account is required. That is their published position as of September 2026, it is a platform decision rather than a rule any vendor sets, and no third-party tool can route around an API that will not accept the account. If your plan was to pipe a signal channel into a futures evaluation account, confirm the current policy with Tradovate and with the firm before you buy the challenge.
WARNING
This is an eligibility rule, not a rules breach — you are not doing anything prohibited by asking. The connection is simply not granted, and the cost of finding that out after buying an evaluation is why it belongs at the top of this article.
Everything below assumes an account the platform will let you connect.
Futures instruments are not names, they are dated contracts. MES is not one thing you trade; MESZ6 is December 2026 micro S&P, MESH7 is March 2027, and they trade at different prices at the same moment. A signal that says GOLD has to become a root and a month before anything can happen.
The mapping rules that do this are short lines you write once per destination. The forms worth knowing:
The row that matters most for signal copying is the fifth. A Telegram channel writes in CFD vocabulary — GOLD, US500, NAS100, EURUSD — because that is what its audience trades. A rule mapping that name to a futures root gets you the front month automatically, and it is re-resolved on a schedule, which stops the mapping pointing at an expired contract eight weeks later.
Write the mapping before you turn the channel on, not after the first trade. A signal for an unmapped instrument is not guessed at — it is skipped, with "no contract mapping" as the reason.
This translation surprises people, because it changes the risk rather than the instrument.
Forex and CFD sizing is effectively continuous: 0.35 lots, or 0.07, or 1.62. Futures sizing is not. You trade one contract, or two, or none. There is no partial position, so rounding is not a cosmetic step.
This is what the micro contracts are for. A worked, illustrative example on gold:
On a 25,000 dollar account with a tight stop, even the micro is too large. That is not a flaw in the copier; it is the market telling you the minimum position size exceeds your intended risk. Two responses are legitimate, and one is not.
The built-in micro-to-mini ratios the copier already knows are worth having in front of you when you are choosing which root to map to:
Ten to one is the common case on index and metal contracts, and it decides whether a signal is takeable on a 25,000 account.
Here the honest answer differs from the intuitive one.
A signal's stop and target are prices on the provider's market. Across CFD and futures those markets do not quote the same number for the same underlying, because a futures contract carries financing and time to expiry that a spot CFD does not. Copying the literal price 3,396 onto a futures account puts a stop at a level that means something different, and sometimes at one already through the market.
So the default is this: the stop and target stay with the Provider, and the futures copy follows the Provider's close. When the Provider's stop is hit, the copy closes. When the Provider's target is hit, the copy closes. The futures account is not trying to reconstruct a price basis it does not share; it is tracking the decision.
That has one implication people should hear before they configure anything: if the Provider disconnects, the futures copy is not protected by a stop of its own unless you set one. A protective bracket on the Follower — a stop placed at the equivalent distance rather than the equivalent price — is the sensible belt alongside that brace, and distance is the concept that travels across the two markets when price does not.
Multiple targets become a scale-out ladder. TP1, TP2, TP3 in a signal is not three targets on one position; it is a plan to close a third at each. On a futures account this runs straight into whole-number sizing again: a one-contract position cannot be scaled out in thirds. Either the position is large enough in micros for the ladder to be meaningful — three contracts, one rung each — or the ladder collapses to a single exit and you should decide which rung it is.
WARNING
A three-rung ladder on a one-contract position does not partially close. Depending on configuration it either exits fully at the first rung or does nothing at the others. Size the position for the ladder, or simplify the ladder for the position.
Futures contracts expire. A December contract stops trading; the volume moves to March. If your mapping points at the front month, it moves too, and it does so while you may have a position open.
Two rules keep this uneventful.
Know your contract's last trading day before you open the position. It is a calendar fact published by the exchange, and ignoring it is the most common way a futures newcomer ends up somewhere they did not expect.
Do not expect a copier to roll a position for you. Rolling means closing one contract and opening another at a different price — a new trade with a new basis and a new cost, which makes it a trading decision. A mapping rule that re-resolves to the new front month changes which contract the next signal trades; it does not touch the position you hold.
The last structural difference. Most futures accounts net: buy two ES and sell one and you hold one long, not a long two and a short one side by side as MetaTrader hedging accounts allow.
Three consequences for signal copying:
Yes, with three things configured: a mapping rule that turns the signal's instrument name into a futures root, whole-number sizing with a rule for what happens when the computed size rounds below one contract, and a decision about stops and targets. Where the signal comes from a CFD or forex provider, the default is that the stop and target stay with the provider and the futures copy follows its close.
From the mapping rule. A rule can pin one month explicitly, carry the Provider's month across to a different root, or resolve to the front month and re-check that on a schedule so it follows the roll. Front-month resolution is the right choice for signals written in CFD vocabulary, because those signals carry no month information at all.
The trade is skipped and logged with the reason, rather than rounded up. Rounding up on a tight stop can be a large multiple of the intended risk, which is why the default is to decline. Mapping to the micro contract instead of the mini — ten times smaller on most index and metal roots — is usually what makes small-account sizing viable.
Only where the position is big enough to divide. Three rungs need at least three contracts, because there is no fractional contract to close. On a one-contract position the ladder is not a ladder, and it is better to choose a single exit deliberately than to discover which rung the system picked.
Not automatically, which is why a protective stop on the Follower matters. The default arrangement has the Provider holding the stop and target, with the copy following its close — so if the Provider is unreachable, nothing is sending a close. Setting an equivalent-distance bracket on the futures side covers that gap, and distance is what translates across markets when price does not.
Not on Tradovate. Their own support documentation states that prop-firm and evaluation accounts are not eligible for the API and that a funded live account is required, which is their published position as of September 2026. This is a platform eligibility rule rather than a rules breach, and no third-party tool can work around an API that declines the account. Verify the current policy with Tradovate before buying a futures challenge you intend to automate.
If you are still deciding whether you need a signal copier or a trade copier — two different machines that get confused constantly — /blog/telegram-trade-copier-vs-signal-copier separates them properly. And the reason a stop price cannot simply be copied from a CFD to a futures contract is the whole subject of /blog/cfd-vs-futures-price-basis.
