This is the whole route for a crypto Algo Provider, in the order you do it: the exchange account you trade at, the symbols you can declare, how your TradingView alerts reach Triggon, the backtest evidence you export, what it costs, what the application asks, and what happens after approval. Nothing on the form should be new by the time you get there.
TradingView is the example here, not the requirement. Triggon authenticates the request and reads its JSON; it does not check what sent it. Your own server, a Python or Node.js bot, or another platform that can send the same authenticated webhook connects the same way. See how the connection works.
This route is open for applications right now.
Sample. Every symbol you declare must pass a test alert in your Hub before the Strategy can go live.
You run a Pine Script Strategy on TradingView that trades crypto pairs on an exchange (spot or perpetual futures), you can configure its alerts, and what you want from Triggon is subscribers and a record rather than a second execution system.
You take the trades yourself, or your process needs judgement a script does not capture. The Manual route needs no TradingView, no code and no alerts. The crypto Manual guide →
Your Strategy trades currency pairs, US stocks or spot metals. Same route, different guide: forex, stocks, commodities.
Eleven steps. The first seven happen before you open the application; the rest happen inside Triggon. Each step links to the section of this page that explains it, and the same list is what the application shows you as its route screen.
Any system that can send an authenticated HTTPS webhook when your Strategy acts: a Pine Script Strategy on a TradingView plan that can fire webhook alerts, your own server or bot, or another platform that can POST JSON. It must cover the symbols you will declare. Triggon never sees your Strategy, only the Signals it sends.
Choose the exchange your Strategy trades on. Triggon never asks a Provider for exchange API keys: the exchange is a fact shown on your Marketplace card, not a connection Triggon makes.
Pick your symbols from the application's picker, spot or futures, up to 10 in one application. Every declared symbol gets its own private connection and must pass a test alert before Go Live.
One alert per declared symbol, firing on entries, stops, targets and exits, with the message shape Triggon reads. The private connection it points at is issued in your Provider Hub after approval.
A TradingView Strategy Tester export (List of Trades, CSV) with the initial capital set to $10,000. A screenshot of the script is optional.
Your public name, a one-line summary, a full description, optional links and images. Subscribers read this before they subscribe.
The Hub creation cost, its validity period, the minimum subscription prices for this market and the platform fee are all stated before you apply, from the current platform settings.
The form collects what you prepared and validates it. The Hub creation cost is charged from your Triggon wallet when you submit.
An admin approves, asks for revisions or rejects, always with a reason. Resubmitting after a revision request is free.
After approval: copy the private connection details, send a test alert for every declared symbol in test mode, verify the health check, then press Go Live.
Go Live lists the Strategy on the Marketplace with the price and seats you set. Every Signal from then on is recorded permanently.
Triggon consumes the alerts your Strategy fires. It never runs your script and never sees its source.
What you need. A Strategy that runs on its own and can send Triggon an authenticated webhook when it acts. On TradingView that means a Pine Script Strategy (a script that places orders in the Strategy Tester, not only an indicator that paints a signal), open on a chart of each symbol you intend to declare, on a plan that can send webhook alerts: TradingView decides which plans include webhooks, so check your plan before you apply, because an alert with no webhook delivery cannot reach anyone. A Strategy that runs anywhere else, on your own server or inside a bot, sends the same request itself and needs no TradingView plan at all: see connect the Strategy you already have. The rest of this section walks the TradingView path, because it is the common one.
Which chart. Open the feed of the exchange you actually trade, for
example its perpetual chart of BTCUSDT. Triggon reads the symbol from the alert and
normalises it: the exchange prefix and any perpetual suffix are stripped, so a chart symbol
such as EXCHANGE:BTCUSDT.P arrives as BTCUSDT, which is how the
symbol is spelled on Triggon's list. If you use your Strategy's per-symbol connection (recommended, see
alerts), the symbol is fixed by the connection and the alert does not
need to carry it at all.
Spot or futures. Decide which instrument your Strategy trades. Spot means the coin itself, held outright, with no leverage; futures means perpetual contracts, with no expiry and no dated contracts, where you declare a maximum leverage. The application asks for one of the two, and every Signal is validated against that declaration.
Alert coverage. A Strategy that alerts on entries but never on exits produces an incomplete record. Plan an alert for every event you want subscribers to see: entries, stop and target updates, partial closes, target hits, stop hits and closes. The TradingView and Pine Script page lists what each alert can express.
Where you trade is your business. Triggon needs nothing from it.
Optionally, the name of the exchange your Strategy trades on, chosen from a list, so subscribers see it on your Marketplace card. That is all. Triggon never asks a Provider for exchange API keys, a login or any credential, and there is nowhere in the application to enter one.
No API key with any permission, no read-only key, no account connection, no balance. If your own setup executes your Strategy on your account, that runs between you, TradingView and your exchange; keep any key you create there without withdrawal permission, as a matter of your own security.
Subscribers who enable Auto-Trade connect their own exchange accounts to have your Signals placed automatically, inside limits they set. Their keys are theirs; a key that can withdraw is refused at connection. Auto-Trade currently supports Binance, Bybit and MetaTrader 5. How Auto-Trade works →
Your Strategy's private connection details and secret are issued in the Provider Hub after approval, are shown to nobody else, and can be rotated at any time. Never paste them into a public script, a screenshot or a message.
You declare your symbols from the application's own picker, and everything on it is a real, priced instrument.
Declare exactly what the Strategy trades. A declared symbol that never sends a test alert blocks Go Live; an undeclared symbol's alerts are refused.
A TradingView alert with a webhook delivery, pointed at the private connection Triggon issues for your Strategy. Here is what to prepare now and what waits for approval.
Write the alert message your Strategy will send, in the shape Triggon reads: the
event type, the symbol, the side, the price, the stop, the targets and their sizes, and a
timestamp from TradingView's own {{timenow}} placeholder. The
TradingView page shows a complete sample. Decide which
events fire an alert. Confirm in TradingView's alert log that your Strategy fires on the
events you expect.
Your Provider Hub's Connection tab issues one private connection per declared symbol and a secret, with ready-made alert messages you can copy. Point each chart's alert at its own connection: the symbol is then fixed by the connection, so one alert per chart is all it takes and the message does not need a symbol field.
Every connection has a test mode that parses and validates an alert completely and stores nothing. Fire your Strategy at it until every check passes. A refusal names its reason: a stop on the wrong side of the price, a target in the wrong direction, a stale timestamp, an unsupported order type.
Records it the moment it arrives, delivers it to subscribers in Telegram and in the app, and adds it to the public record. Exact repeats are acknowledged once and never applied twice, so TradingView's retries are safe. Business rejections are answered in a way TradingView will not retry.
The review looks at how the Strategy has behaved. For a crypto Strategy that is a TradingView export; after approval the same file is imported as the Strategy's historical record.
..._BTCUSDT_...) so the import knows which market each file describes.Imported history is marked as imported. It does not count towards the Verified checkmark, which describes Signals Triggon itself recorded as they happened. What Verified means →
Your name, email and country come from your Triggon Profile and are shown read-only in the application. Complete them in Settings before you start.
A unique English name, a one-line summary for the Marketplace card (up to 30 characters), a full description, up to three trading styles, a risk level, and the cadence: how often it fires and how long a position typically runs.
Optional: your website and social handles (usernames only; Triggon builds the links), a logo (500×500), a banner (1500×500), a profile picture and a cover image.
Read live from the platform settings, the same ones the wallet charges from.
An illustration computed from the live fee rate, not a forecast or a guarantee. Actual earnings depend on how many seats fill, cancellations and their refunds, promotions a subscriber used, and any automatic Hub top-up taken from a sale. What decides what you earn →
Opened in Telegram. It starts by confirming the route you chose here, shows this guide as a link on every step, and asks only for what this page told you to prepare.
Provider info (contact details), then the Strategy: name, summary, description, styles, risk level, market: Crypto (fixed from your route), Spot or Futures, position mode, the symbols from the picker, the exchange (optional), timeframes, the leverage mode and band, the take-profit method, the maximum capital risk per position, your prices and your seat cap. Then the uploads (backtest export, screenshot, report), branding, operations (cadence, timezone, sessions, off days, an optional Signal footer), and the review. You are not asked what fees to assume: Triggon applies the same maker and taker rates to every Strategy, so published results stay comparable.
No API keys, no exchange credentials, no connection details: those are issued to you after approval, not collected from you. No take-profit ladder: targets are a per-Signal decision. No drawdown claim: drawdown is measured from the record.
Every step is saved on the server as you go. Leave and come back and you continue where you stopped, with your route, your market and your answers preserved. Nothing sensitive is stored in your browser.
A route-specific checklist, the one at the end of this page, must be confirmed item by item, and the fee and pricing recap is shown once more. Then Submit and Pay.
The part that could not happen before approval.
Every Signal from Go Live on is permanent and public. Subscribers pay from their Triggon wallet, your share lands in yours, and you withdraw when you choose. Once 20 trades have closed over 30 live days, the Strategy is ranked on the Leaderboard by its Triggon Score.
Complete Signals, an entry with a stop and at least one target, and management of what you open. Keep the Strategy running: a Strategy that goes silent is warned, and then suspended from the Marketplace with its subscribers told, which is worse for a record than a losing month.
Prices (above the minimum), seats, pausing, Hub recharges: yourself, in the Hub. Description, links, images and declared trading facts: reviewed before they go live.
The route (Algo), the market (crypto) and Spot or Futures are fixed at application. A different route or market is a new Strategy.
These are the items the application asks you to confirm before Submit and Pay on the crypto Algo route. If every line is true, you are ready.