A test mode that records nothing
Every Strategy gets a validation mode that parses and checks an alert completely without storing a Signal. You can fire your Strategy at it as many times as you like while you get the alert configuration right.
Algo Providers
Your Strategy already generates the Signals. Triggon distributes them.
An Algo Provider runs a Strategy that produces its own entries and exits, usually a Pine Script Strategy on TradingView, and connects it to Triggon with webhook-supported alerts. Each alert becomes a Signal for your subscribers, recorded permanently.
Connection · test modeRecords nothing
✓BTCUSDT09:14 alert parsed · entry, stop, 2 targets · validated
✓ETHUSDT09:16 alert parsed · entry, stop, 1 target · validated
✗SOLUSDT09:18 refused: stop on the wrong side of the price for a long
✓SOLUSDT09:21 alert parsed · stop below entry · validated
Go-live gateReady to publish
Declared markets passed3 / 3
✓Connection confirmedeach market
✓Application approvedreason on record
✓Hub validPending to Live
✓Connection details privaterotatable any time
Sample. A Strategy cannot go live until every market it declared has produced a successful validation.
The route, end to end
Step 01
Your Strategy
A Pine Script Strategy on TradingView that you already run. You do not rebuild it.
Step 02
Webhook alerts
Configured to fire on the events your Strategy produces: entries, exits and the management in between.
Step 03
Triggon
Validates each alert, records it, and turns it into a Signal.
Step 04
Subscribers
Receive the Signal in Telegram, with your Strategy's record attached.
Step 05
Auto-Trade
Places it on the accounts of subscribers who enabled it, inside their own limits.
What Triggon accepts from an Algo Strategy
A full position lifecycle, not just entries. Everything your Strategy does to manage a trade can be expressed.
EntryOpens a position with its direction, price, stop loss and take-profit levels.
Add to positionA further leg under the open position, for a Strategy that scales in.
UpdateRewrites the stop loss and/or the targets on an open position.
Partial closeReduces the position by a share you specify, leaving the rest open.
Target hitRecords a take-profit level being reached and the share it closed.
Stop hitCloses the position at the stop, recorded like any other close.
CloseEnds the position and every leg under it.
One-way or hedgeOne direction at a time per market, or long and short simultaneously.
Sizing and leverage can travel with a Signal too. Both are treated as ceilings on the subscriber's side: a Signal can ask for less than a subscriber allows, never for more.
Nothing goes live untested
Every declared market must pass
A Strategy cannot be published until it has produced a successful validation for each market it declares. An integration that works for one symbol and silently fails for another is caught here rather than by a subscriber.
Your connection is private and rotatable
Each Strategy has its own connection details and its own secret, both issued in the Connection tab of your Provider Hub and rotatable at any time. They are never shown on a public page.
Bad Signals are refused, not forwarded
A stop on the wrong side of the price, a target in the wrong direction, an unsupported order type, a stale timestamp: each is rejected at the door, before it can reach a subscriber's account.
Is the Algo route right for you?
Yes, if
You have a Strategy that already runs automatically, you can configure its alerts, and your problem is distribution rather than signal generation.
Consider Manual instead, if
You trade discretionarily, or your process involves judgement a script does not capture. The Manual route publishes to the same Marketplace and builds the same record.