Automate the TradingBrain signals with Alerio
Alerio reads our signals on Discord and places them in your futures account. It can read them from either of two channels — #automated-signals or #bot-signals. You choose the channel and the size. It runs on Alerio's side, not on your screen. This guide covers only the TradingBrain-specific settings — Alerio's in-app onboarding handles the rest.
Two ways to automate
Both channels carry the same signals — same entries, stops and targets. They place the entry differently, so each one fills better in different moments.
Built for automation: one line of text per action, always in the same format.
- ENTRY — a limit order with its stop, Target 1 and final target.
- MOVE SL — at +40 pts in favor before Target 1, the stop moves halfway toward the entry.
- CANCEL — your limit should no longer fill. Alerio doesn't support this line yet and ignores it (Alerio team, Oct 28), so the Cancel order in timer is what removes an unfilled limit.
The limit goes at the signal's entry, or at the current price when the signal says "take the entry now". A late signal sends no order. One signal at a time.
Alerio reads the full signal card and enters as soon as it lands, so you're in fast even when the signal moves right away.
⚠ In Alerio, a "Market" entry goes in as soon as the card lands, whatever the price. To avoid chasing, turn on Ignore if over threshold by: if price is already that many ticks past the entry, Alerio skips the trade (Alerio team, Oct 28).
Which one? A is the one designed for automation: its format was agreed with Alerio and doesn't change when we restyle the cards, while B depends on the text of our cards. Both can work — what changes the result is your Alerio setup: order type, entry offset, order expiry and how you take profits. The choice is yours.
0 What you need
• An active TradingBrain Premium membership — access to #automated-signals and #bot-signals.
• An Alerio Futures Alert Copier plan.
• A supported futures account: Tradovate, NinjaTrader (Tradovate-based connection) or Rithmic.
enough for TradingBrain
if you follow more sources
same features, more room
Same features on every tier — they differ by capacity only. Prices as published by Alerio.
Sign up at tradingbrain.dev/alerio
That's TradingBrain's official Alerio affiliate link — TradingBrain may earn a commission if you sign up through it, at no extra cost to you.
TradingBrain is an official Alerio affiliate, not a joint venture: Alerio is the automation platform, TradingBrain is an independent signal provider.
1 Sign up and connect the signal channel
Get your plan at tradingbrain.dev/alerio — our affiliate link, TradingBrain may earn a commission at no extra cost to you — then log in at app.alerio.dev/login (sign-in runs through Whop). Complete Alerio's onboarding first. Then connect the channel you picked as a source — you'll need its Channel ID:
There are two ways to connect a channel. Pick one — not both, or every alert arrives twice.
- Alerio → Sources → Webhook → save it.
- Open the route → ? next to Save → paste the Channel ID → Copy configured script.
- Paste it into Tampermonkey or Violentmonkey as a new script.
- Keep Discord Web open on that channel. Forwarding stops if that tab closes.
- Alerio → Sources → Discord → paste your Discord account token.
- New Route → paste the Channel ID → save.
- Runs 24/7 without your browser.
⚠ It uses a user token, which Discord's terms technically don't allow for third-party software. Alerio explains the trade-off in their Discord guide — read it and make your own call.
Before you go further, confirm the source shows Online and that a message from that channel appears in Alerio's Logs.
Alerio docs: Getting started · Discord source · Browser forwarding
2 Connect your broker and set your size
Alerio → Accounts → Futures → connect Tradovate or Rithmic (NinjaTrader accounts connect through Tradovate). Then add one NQ contract row for that account:
Tradovate setup · Rithmic setup
3 Route settings for TradingBrain
Open the route you created and set it like this. Setting names are as they appear in Alerio. A value in bold is what our message format needs; your call depends on your account and your risk.
A · #automated-signals — every instruction is one line like these:
| Setting | Value · why |
|---|---|
| Entries, Trims, Exits | |
| Entry order | Limit · offset 0 — the limit price comes in the line. |
| …that expires in | your call, no later than 4:00 PM ET. Our limit waits for price to come back to the entry, so it often fills late: on Oct 7, signal #3 posted LMT 31275.00 at 11:14 ET and price only came back to it in the 11:21 candle — a 240-second expiry would have cancelled it first. We recommend 900 sec (15 min), and don't leave it off: Alerio doesn't act on our CANCEL line yet, so this timer is what removes a limit that never filled. Optional: Offset entry price by gives the limit room (Alerio suggests ~10–20 pts), at a worse price and fewer micros. |
| Stop loss | Fixed · Should use alert SL — uses the stop in the line. The fixed value only applies if an alert has no stop. |
| Trim levels · Runners | your call — how much to close, where, and where the stop goes after each trim. The channel's pinned note suggests the stop to break-even when Target 1 fills. See "Your risk, your call" below. |
| Advanced · Limit Order Type | your call — Quote Fallback is the default: it uses the alert's price. |
| Execution | |
| Which accounts should receive these alerts? | your call — start with one test account. Contract type (NQ or MNQ) and size are set on each account. |
| Should trim alerts be allowed? | No — this channel sends no trims; yours come from your Trim levels. |
| Should stop-loss adjustments be allowed? | Yes — so MOVE SL reaches your position. |
| Should exit alerts be allowed? | your call — it doesn't change our CANCEL: Alerio doesn't support that line yet and ignores it either way (Alerio team, Oct 28). Alerio cancels working orders only when it processes a trim or an exit alert. |
| Should multiple positions be allowed? | No — we post one signal at a time. |
| Half-size entries · When a live entry cannot be placed | your call — our lines never ask for half size. "Allow Dry Run" simulates the entry when it can't be placed live. |
| Session Controls | |
| When should positions close automatically? | your call — we don't send a close for an open position: this is what flattens it. The channel's pinned note suggests 3:58 PM ET, when our bot closes anything still open. |
| Market events · Time window | your call — signals come out in the New York morning session. |
| Parser | |
| How should alerts be interpreted? | AI |
| Should profit updates alerts trigger trims? | No |
| Do the alerts omit the ticker? | No — every line says NQ. |
| How should TP and SL prices be interpreted? | Auto — the prices come in full. |
| Contract Mapping | Disabled — if enabled, Alerio ignores the line's entry, TP and SL. |
| Extra AI instructions | your call — the fixed format doesn't need them. |
B · #bot-signals — Alerio reads the full signal card:
| Setting | Value · why |
|---|---|
| Entries, Trims, Exits | |
| Entry order | Market — Alerio enters as soon as the card lands, whatever the price. Turn on Ignore if over threshold by to skip the trade when price already ran that many ticks past the entry. |
| Stop loss | Fixed · Should use alert SL — uses the card's stop. |
| Trim levels · Runners · Advanced · Minimum Trim | your call — see "Your risk, your call" below. |
| Execution | |
| Which accounts should receive these alerts? | your call — start with one test account. |
| Should half-size entries be allowed? | your call — when price is already past the entry, the card says "with smaller size". With Yes, Alerio can enter half size on those cards; with No, full size. |
| Should trim alerts be allowed? | No — our information messages ("Scale-out", "Runner update") can be read as trims. For one member, a "Runner update" from another signal closed the position. |
| Should exit alerts be allowed? | No — same reason. |
| Should stop-loss adjustments be allowed? | your call — with Yes, Alerio follows the stop moves the channel posts (break-even at Target 1, halfway at +40). |
| Should multiple positions be allowed? | No — one signal at a time. |
| What should happen when a live entry cannot be placed? | your call — "Allow Dry Run" simulates the entry; the other option ignores it. |
| Session Controls | |
| When should positions close automatically? | your call — with exit alerts off, this is what closes a position still open at the end of the day. Our bot closes anything still open at 3:58 PM ET. |
| Market events · Time window | your call — signals come out in the New York morning session. |
| Parser | |
| How should alerts be interpreted? | AI — the card is free text. |
| Should profit updates alerts trigger trims? | No — our progress messages ("+X pts and running") are not orders. |
| Do the alerts omit the ticker? | NQ — look at the signals above: the "NQ" sits inside the chart image, not in the message text. Alerio reads text, not pixels. |
| How should TP and SL prices be interpreted? | Auto |
| Advanced · Ignore alerts that include… | watch · watching · on watch · watchlist · recap · summary · pts past the entry · DEMO — "pts past the entry" shows up when price has already moved away from the entry, so you don't enter late. DEMO marks a test message, never a real signal. |
| Contract Mapping | Disabled — if enabled, Alerio ignores the card's entry, stop and targets. |
| Extra AI instructions (General) | the block below — copy and paste it as is. |
AI parser · Entry order policy
4 What each message does
A · #automated-signals
| Message | What Alerio does |
|---|---|
ENTRY … TB-SIGNAL-n | Places the limit entry with its stop, Target 1 (TP1) and final target (TP2). TB-SIGNAL-n is the signal's number for the day, so you can match its messages at a glance — Alerio's parser ignores it. |
MOVE SL NQ … (at +40, before Target 1) | Moves the stop of the open position halfway toward the entry — only with "Should stop-loss adjustments be allowed?" = Yes. If price never reached your limit, a CANCEL goes out instead. |
CANCEL NQ … | Sent when the signal no longer wants your limit: Target 1 came first, price ran +40 pts without reaching it, the signal ended, or it's 4:00 PM ET. Alerio doesn't support this line yet and ignores it, filled or not (Alerio team, Oct 28): it never touches an open position, and it doesn't remove an unfilled limit either — your Cancel order in timer does (we recommend 900 sec). |
| Target 1 | No message. What happens at Target 1 (trim, stop to break-even) comes from your route's Trim settings. |
| Session start · Session end | Nothing: day markers, not orders. Session start at 9:30 AM ET; Session end right after the 12:00 PM ET close. After it there are no new ENTRY lines, but an open signal can still get its MOVE SL or CANCEL. |
| A late signal | Nothing is posted here — no ENTRY. |
| End of the day | No close message: a position still open is closed by your Session Controls. |
B · #bot-signals
| What the card says | What Alerio does |
|---|---|
| SIGNAL VALIDATED · ⚡ Direct signal | An entry: Entry, Stop, Target 1 and Final target. |
| Scale-out · Target 1 hit · Runner update · TRADE CLOSED #1 / #2 | Information for traders who follow by hand. With trim and exit alerts set to No, Alerio doesn't trim or close on them: your Trim levels, the alert's stop and targets, and your Session Controls handle the exit. A stop move in them (break-even at Target 1) is followed only with stop-loss adjustments = Yes. |
Automated users ONLY. Move NQ stop to X. (at +40, before Target 1) | Moves your stop to X — risk on the trade cut by 50%. Only if "Should stop-loss adjustments be allowed?" = Yes. |
⚠️ Price is N pts past the entry. on a SIGNAL VALIDATED | Information, not an order: the signal is still valid, but price has already moved N pts from the entry — a later fill means more risk against the same stop. With "pts past the entry" in your ignore list, Alerio skips the card. |
A ⛔ SKIP card (same ⚠️ Price is N pts past the entry. line) ending in Automated users ONLY. Do not enter — price already past the entry. | No entry: price ran too far before the signal went out. In the Alerio logs we've reviewed, these cards came back as "Alert is not actionable" — no order placed. If your Logs ever show an entry from a SKIP card, tell us in #tradinghelp. |
🟡 TRADE IDEA #N — LONG/SHORT · waiting for the zone, with Entry / Stop / Target 1 / Final target and ending in Automated users ONLY. Do not enter — not a position, waiting for the zone. | Nothing to take: the setup confirmed late, so it goes out as an idea — not a position. A signal comes out only if price comes back to the zone and reacts; if not, the idea is cancelled. When the idea closes, the card is edited and its last line reads Automated users ONLY. Do not enter — not a position; this idea is closed. If your Logs ever show an entry from a Trade Idea, tell us in #tradinghelp. |
| #1 / #2 | The trade number of the day. It does not select Alerio's Target 1 or 2. |
Brackets & stops · Parser keywords
Your risk, your call
These are yours to set for your own account: contracts per account, how much to trim and where (RR), runners, the auto-close time and half-size entries.
One member's example — not a recommendation. Two setups a member shared, one per channel. The values are theirs, not a suggestion from us.
| A · #automated-signals | B · #bot-signals | |
|---|---|---|
| Entry | Limit · offset 0 · expires in 900 sec (15 min) | Market |
| Trim 1 | 60% at Target 1 (or 1R) → stop to +10 pts | 20% at 0.5R → stop to +2.5 pts |
| Trim 2 | 40% at 2.2R → stop to entry | 80% at 1.1R → stop to entry |
| Runners | 0% | 0% |
| Half-size entries | Yes · 50% | Yes · 50% |
| When a live entry can't be placed | Allow Dry Run | Allow Dry Run |
| Trims and exits without a ticker matched by | Closest Alert P&L (trim only) | Most Recent Position |
| Stop-loss adjustments | Yes | No |
| Auto-close | 3 PM ET | 3 PM ET |
With these setups, the member exits before the signal's final target and goes flat at 3 PM ET, before our management ends. That's a valid choice — just make it knowing that.
5 Validate once, then let it run
The goal isn't to watch every trade. Validate the path once, then only open Logs when you change something or something looks off.
Before real money, confirm: Live Orders on · the intended account · only the routes you mean to run · contract type and size right on each account (NQ or MNQ) · "Should use alert SL" on · your Trim levels and auto-close time set · on #automated-signals: "Should stop-loss adjustments be allowed?" = Yes and a limit expiry you chose · on #bot-signals: trim and exit alerts = No, the ignore list and the Extra AI instructions in place · in the test run, every message did what you expected.
Alerio setup, broker or parser issues → Troubleshooting · Alerio support. Questions about the signals themselves → #tradinghelp in our Discord.
Automation executes our signals in your account with your risk. We publish every result, losses included — but what runs in your account is yours, and since your exits come from your own settings, it can end differently from the trade we track. Test in Dry Run first, size like you'd size by hand, and never attach an account you can't afford to run on autopilot.
Ready? tradingbrain.dev/alerio
Our affiliate link — TradingBrain may earn a commission, at no extra cost to you.
Versión en español →