If your Strategy already runs as a Pine Script on TradingView, you do not rebuild it for Triggon. You point its alerts at Triggon, and Triggon does the distribution: turning each alert into a Signal, sending it to your subscribers, and recording it permanently.
This page is about the TradingView route specifically. It is the most common way to send Triggon a Signal, and it is not the only one: Triggon's Algo connection is a plain authenticated webhook, so a Strategy running on your own server, in a Python or Node.js bot, or on another platform that can send the same request connects just as well. If that is you, start at how the connection works instead.
Sample alert. Your Pine Script never leaves TradingView. Triggon receives the alert, not the logic that produced it.
Pointing a TradingView alert at a webhook is one mechanism used for two quite different purposes. Triggon does one of them, and it is worth checking now which one brought you here.
Your Pine Script fires, the alert reaches Triggon, and it becomes a Signal delivered to people who subscribed to your Strategy and recorded permanently as it happens. You are publishing. The application is reviewed before the Strategy goes live, and the record it builds is public.
Triggon is not a private relay between your alerts and your own account. There is no setting that takes your webhook and trades your balance from it without a published Strategy behind it. If a personal order router is what you are looking for, this is not that tool, and it is better to know before you read the rest of this page.
The two do meet at one point. Once your Strategy is live, you may run Auto-Trade on it yourself like any other subscriber, so your own alerts can end up placing orders on your own account. What you cannot skip is the publication that comes first.
Running on TradingView, exactly as it does today.
Fires when your Strategy triggers, carrying what the trade is.
Validates it, records it, and publishes it as a Signal.
Receive it in Telegram, with your track record attached.
Places it for subscribers who enabled it, in their own accounts.
Your connection details and the secret that authenticates your Strategy are issued privately in the Provider Hub after your application is approved. They are never published, and they are rotatable at any time.
A complete position lifecycle. Everything your Pine Script does to manage a trade has a corresponding Signal, not just the entry.
No. Triggon consumes alerts; it does not run your Pine Script. What you may need to add is alert coverage for the events you want subscribers to see. A Strategy that alerts on entries but not exits produces an incomplete record.
No. Triggon never sees your Pine Script. It receives the alerts your Strategy fires, not the logic that produced them.
It is rejected with a specific reason and never becomes a Signal. Rejections are returned in a way TradingView will not retry, so a Provider error cannot become a retry storm.
Triggon recognises an exact repeat and acknowledges it without acting on it a second time. A duplicate alert cannot open a duplicate position.
Yes. Declare each market when you create the Strategy, and each must pass validation before the Strategy goes live.
At any time, from your Provider Hub. Rotating issues a new secret and invalidates the old one immediately.