Skip to main content
Automations require the Trader plan or above. See plans.
We’ll build a real one end to end: notify me on Discord when NVDA is oversold on above-average volume. Ten minutes, and the pattern generalises to anything else you want to watch. Every automation is a left-to-right flow on the canvas. Only the ends are compulsory:
What each node does is set out in the five node types.

​
1. Create it

Open Automations in the sidebar and click New automation. You get two options: Start from scratch, or Use a template. Pick start from scratch — there are 45 templates and they’re worth browsing later, but building one yourself is how the pieces make sense. Either way you land on the same canvas.
The automation canvas, showing a node palette on the left and a connected graph of asset, condition, logic, agent, and action nodes

The canvas builder. Drag from a node's handle to connect it to the next one.

​
2. Set the asset

Click the asset node and search NVDA. Tradion shows the live price as you type so you can confirm you’ve got the right instrument.
The signal types available downstream depend on asset type. Earnings and Options Flow are stocks-only; Price, Volume, and Change % work for everything.

​
3. Add the first signal — RSI

Click the condition node and configure:
RSI is the Relative Strength Index — a 0 to 100 score measuring how hard a stock has been pushed in one direction recently. Below 30 is conventionally called oversold, meaning sold down far enough that some traders expect a bounce. That convention breaks down in a strong downtrend. The dropdown offers Crosses Below (one-shot) and Goes Below (continuous). Pick the crossing one: it fires on the single check where RSI passed through 30, while the continuous one stays true for as long as RSI sits under 30 — eighty alerts about the same afternoon. Full explanation: operators.

​
4. Add the second signal — volume

Click + Add condition. A logic node appears automatically between your signals.
The number you type is a multiple of normal, not a share count. 2 means twice the average, 1.5 means half again as busy as usual. Tradion works out “normal” from the 20 bars before the current one, so today’s own trading doesn’t get counted into the average it’s being measured against.
Volume has no operator dropdown — the check is always above. You’re asking “is it busier than N times normal right now?”

​
Picking the number

Start at 2 and adjust. Below about 1.5 you’ll catch ordinary busy mornings; above 3 you’ll only see genuine events, and on a quiet symbol you may see nothing for months.
A symbol needs at least 11 bars of history for the average to mean anything. Newly listed tickers and young option contracts report no average volume available and the condition won’t fire until enough history exists.
Set the logic node to AND — you want both true at once, not either.

​
5. Choose where the alert goes

Click the action node and turn on a channel. For this one, pick Discord: paste a webhook URL from your server (Server Settings → Integrations → Webhooks). Email, Telegram, in-app, and your own webhook endpoint all work too, and you can turn on several at once — setup for each is in notification channels.
Telegram is the one with a hidden step. There is no Telegram panel in Settings: you message the bot first, then paste a numeric chat ID into this node. Notification channels has the procedure.
Then write the message. Template variables use single braces:
A name that isn’t a real variable is printed literally rather than replaced, so check your spelling against the list in notification channels.

​
6. Sanity-check the threshold

Tradion has no built-in frequency estimator, so do this by eye before you switch the automation on. Ask AI Quant Research how many times in the past year NVDA’s daily RSI crossed below 30, then decide whether that many messages is something you would still read in month three.
A handful of alerts a month gets acted on. Forty a day gets muted, and a muted alert is worth nothing.
Too frequent? Tighten the threshold, lengthen the timeframe, or switch a Goes operator to a Crosses one.

​
7. Activate

Toggle Active. Tradion picks the automation up within 60 seconds and re-checks it every 60 seconds after that. Some automations get checked faster. If every signal on the canvas is a price or volume check on a US stock, Tradion also watches the live trade feed between 9:30 AM and 4:00 PM ET and reacts within about a second of the trade that makes your condition true. Our NVDA example has an RSI signal on it, so it runs on the 60-second cycle.
Automations run around the clock, not only during market hours. Outside regular trading the last available values are what get checked, so a condition that was true at the close can stay true overnight. A cooldown is what stops that turning into a stream of alerts.

​
In plain English

The 60-second cycle is a heartbeat. Once a minute Tradion asks: are all the conditions on this automation true right now? If they are, and no cooldown is running, it fires. If a condition went true and false again between two checks, nobody sees it — which is why conditions built around levels that hold for minutes work better than ones that hold for seconds.

​
Adding an AI agent (optional)

Drop an Agent node between the logic and action nodes and the message arrives as a short research brief — news, filings, insider activity — instead of a bare price alert. Agent nodes spend from a monthly allowance, 50 runs on Trader and 500 on Quant, so keep them off high-frequency triggers. Details: the AI Agent node.

​
The two mistakes people make here

You picked Goes Above (continuous) or Goes Below (continuous) where you wanted the Crosses version. Fix the operator first, then add a cooldown. See operators.
Usually the volume number is too high, or RSI never actually reached 30 — check a chart rather than assuming. Runs and history has the full check-in-order list.

​
Next

All 9 signal types

Including options flow, insider filings, and corporate actions.

Runs & history

Debug what fired, when, and why.