Axiom Flow
Correlates your TradingView alerts across timeframes and forwards the ones that agree to Telegram.
An alert on its own tells you one thing about one timeframe. Axiom Flow stores what each alert said as a named state, checks every new alert against those states, and delivers only the ones that line up.
How it works
One webhook in, one delivered message out — and four steps in between that you configure yourself.
TradingView fires an alert at your webhook endpoint, carrying the symbol, the timeframe and whatever the indicator had to say.
The prism fans that one alert out by rule. Its routes decide which states get written and which signals get evaluated.
Read moreWhat survives is delivered to a destination — a Telegram topic, a Discord channel, or a webhook of your own.
Read moreOne alert in, every platform out
A prism receives alerts on a single webhook and fans each one out through a routing table. Routes match on the alert text itself — symbol, strategy, phrases like FILLED — so one broad TradingView alert sorts itself.
TradingView caps your active alerts, and each alert carries exactly one webhook URL. With a prism, that one URL is all you spend: adding a Telegram group, a Discord server, a second environment or a broker webhook is a route edit here — never another alert slot there.
- Reuse the same alert across Telegram, Discord and webhooks
- Route to live and staging side by side, pause either alone
- Feed states, signals and channels from a single hit
Facts that outlive the alert
An alert is gone the moment it fires. A state keeps what it said: the storage filter picks out the fragment that matters and holds it as a named fact — btc-4h holding “Bullish Trend Started” until the next trend event replaces it.
Do that per symbol and timeframe, and you have a live snapshot of the last important event everywhere on your watchlist — the memory that every new alert gets judged against.
- The filter keeps the important events; the noise never overwrites them
- One fact per key — btc-4h for the trend, btc-4h-range for range breaks
- All keys together form a snapshot of what your indicators last said
Only the important signals get through
A signal first reads which way the alert points — long or short — then runs it through logic gates built on your states. Each direction has its own conditions: a long can demand that the higher-timeframe trend is bullish, a short that it is bearish.
That is trading with the trend, automated. If the 1-day is trending up, 1-hour longs pass and 1-hour shorts are blocked. The noise never reaches your phone — what does arrive is already in agreement with the bigger picture.
- Direction first: long and short each get their own gate
- AND/OR logic gates over any of your states — trend, range, both
- Fewer pings, each one worth looking at
Where messages actually land
A destination is a reusable delivery target — a Telegram topic, a Discord channel, or a webhook pointing at any external system of yours. Prisms, states and signals all point at the same destination records.
A passing signal fans out to all of its destinations at once — several Telegram topics, a Discord channel, webhooks. A webhook can have a transformation in front, shaping the alert into the payload your system expects — or take the raw alert untouched. And each destination can be paused on its own, without touching anything upstream.
- Transform the alert into the payload your system expects — or pass it raw
- Telegram topics and Discord channels created from the app
- Pause a route, a mapping or a destination — three distinct levels
Features
Everything is configured from the dashboard, and everything is inspectable after the fact.