TRIGGON Open in Telegram
TradingView & Pine Script

Keep your TradingView Strategy. Add an audience.

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.

Apply in Telegram The Algo Provider route

How a TradingView alert becomes a Signal

01

Pine Script Strategy

Running on TradingView, exactly as it does today.

02

Webhook alert

Fires when your Strategy triggers, carrying what the trade is.

03

Triggon

Validates it, records it, and publishes it as a Signal.

04

Subscribers

Receive it in Telegram, with your track record attached.

05

Auto-Trade

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.

What your alerts can express

A complete position lifecycle. Everything your Pine Script does to manage a trade has a corresponding Signal, not just the entry.

EntryDirection, price, stop loss, and one or more take-profit levels with per-level sizing.
Scale inAdditional legs under the open position, shown to subscribers as one position.
UpdateMove the stop or rewrite the targets on a running position.
ReduceClose part of the position without a target being hit.
Target hitRecord a take-profit level and the share it closed.
Stop hitClose at the stop, recorded like any other exit.
CloseEnd the position and all of its legs.
One-way or hedgeOne direction per market, or long and short at once.
Leverage & sizeTravel with the Signal as ceilings: a subscriber's own limits always win.

Getting connected

  1. Apply as a Provider. Approval comes before any connection is issued.
  2. Create your Strategy on Triggon and declare every market it trades. The declaration matters: it is what the validation step checks against.
  3. Collect your connection details from the Connection tab of your Provider Hub. They are private to that one Strategy.
  4. Configure your TradingView alerts to fire on the events your Strategy produces, and point them at that connection.
  5. Run the test mode. Alerts are parsed and validated completely without recording a Signal, so you can iterate freely. You will be told exactly what is wrong when something is.
  6. Pass every declared market. Triggon will not let the Strategy go live until each one has produced a successful validation.
  7. Publish, and start building the record.

Common questions from Pine Script authors

Do I have to change my Strategy's logic?

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.

Does my Strategy's source code leave TradingView?

No. Triggon never sees your Pine Script. It receives the alerts your Strategy fires, not the logic that produced them.

What happens if an alert is malformed?

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.

What if the same alert fires twice?

Triggon recognises an exact repeat and acknowledges it without acting on it a second time. A duplicate alert cannot open a duplicate position.

Can I trade several markets from one Strategy?

Yes. Declare each market when you create the Strategy, and each must pass validation before the Strategy goes live.

Can I rotate the credentials?

At any time, from your Provider Hub. Rotating issues a new secret and invalidates the old one immediately.

Apply in Telegram Read the FAQ