Your alerts should arrive.Every time. With proof.
Send TradingView webhooks into Tickory. Route alerts to Telegram, Discord, email, or your bot with retries, replay, and a full downstream trace.
TradingView still fires the alert. Tickory handles routing, recovery, and proof downstream.
Built for alerts that trigger something real
Use TradingView webhooks or Tickory scans. This page focuses on the TradingView relay path for teams that already have downstream routing or automation in place.
Inbound event
BTC breakout confirmed
Why this exists
Built for alerts that trigger something real
If one inbound TradingView alert needs to reach several destinations, survive downstream failures, and stay debuggable, Tickory gives you a managed control plane instead of another relay script.
Fan-out from one inbound alert
Point TradingView at Tickory once, then route the same alert to Telegram, Discord, email, or your bot.
Recovery when a destination fails
Tickory can retry downstream delivery and keep the failure visible instead of leaving you to debug custom relay glue.
End-to-end trace with proof
See when the alert arrived, which routes matched, what delivered, and what still needs replay.
Why Tickory instead of raw TradingView webhook?
Replace your custom relay stack
TradingView can send to one URL with basic retries and status. Tickory adds fan-out, richer recovery, dedup, and a clearer downstream trace.
Raw webhook stack
- One destination per alert unless you bolt on your own fan-out.
- Route-level failures live across logs, bot dashboards, and relay scripts.
- Duplicate handling and replay are custom glue you own forever.
Tickory relay path
- One inbound source fans out to Telegram, Discord, email, or webhook destinations.
- Per-route delivery attempts, receipt proof, and replay stay visible in one trace.
- Less glue code once you need fan-out, dedup, and recovery after the alert fires.
Workflow
What changes after the alert fires
Before
- TradingView points at custom relay scripts.
- Telegram, Discord, and bots fail in different places.
- You debug by stitching together logs after something breaks.
After
- TradingView points to one Tickory source.
- Tickory fans out through direct routes and keeps failures visible.
- Replay is available from the trace when a downstream route needs recovery.
FAQ
What sources are supported now?
This relay flow is built for inbound TradingView webhooks. Tickory scans can also generate alerts inside the product, but this page is specifically about the TradingView path.
Does Tickory replace TradingView or fix alert firing?
No. TradingView still handles signal generation and firing. Tickory handles what happens after the webhook is sent: routing, retries, replay, and a clearer downstream trace.
How is this different from a raw TradingView webhook?
TradingView can send to one URL with basic retries and status. Tickory adds fan-out, route-level visibility, delivery recovery, replay, and less glue code once you start chaining destinations together.
What does dedup mean in practice?
Tickory suppresses repeated source events before they fan out through the same route, so a duplicated upstream payload does not keep triggering the same downstream path.
Start with the real path
Connect TradingView, then inspect the trace
Start the beta setup, create a TradingView source, add a direct route, and send a test alert through the trace before you trust it with live traffic.
Beta access is still limited while we validate this relay workflow.
Safety & compliance
Tickory is a monitoring and alerting tool. It does not provide trading advice, profit claims, or automated execution. You own your decisions and risk management.
TradingView still controls signal generation and firing. Tickory handles downstream routing, retries, replay, and proof once an alert reaches the relay path.
Operational fit
This workflow is for users who already route alerts into bots, Telegram, Discord, or custom webhooks. If your main problem is TradingView logic or upstream firing delays, Tickory is not the layer that fixes that.