Connect TrendSpider alerts to Nyria
Send TrendSpider alerts and Strategy Bot signals to Nyria as webhooks so connected brokers execute the trade automatically. Includes copy-paste payloads using TrendSpider's real %alert_symbol% / %bot_symbol% variables.
By the end you will have TrendSpider firing a webhook into a Nyria strategy that routes the resulting order to your connected broker, with the symbol and price coming straight from TrendSpider's own variables.
TrendSpider is live — pick it as a strategy's alert source in the Integration tab. Nyria's parser is source-agnostic, so a TrendSpider payload is handled exactly like a TradingView or custom-API alert; if you've shipped a TradingView setup this takes about ten minutes.
Two ways TrendSpider fires webhooks
TrendSpider has two webhook surfaces, and they behave differently — pick the one that matches how you trade:
| Alerts (price / indicator / scanner) | Strategy Bots (TrendSpider's automated strategies) | |
|---|---|---|
| Webhook URL | One global URL per account (Account & Settings) | Per-bot URL and body |
| Symbol variable | %alert_symbol% | %bot_symbol% |
| Route to multiple Nyria strategies? | No — every alert hits the one account URL | Yes — each bot can target its own Nyria strategy token |
Rule of thumb: if you want one TrendSpider account driving several Nyria strategies, use Strategy Bots (each bot gets its own webhook URL). Plain Alerts all share a single account-level URL, so they can only feed one Nyria strategy.
TrendSpider's variables
These are the exact tokens TrendSpider substitutes when a webhook fires — note
the %...% syntax (not {{...}}):
Alert webhooks
%alert_symbol%— the symbol the alert fired on%last_price%— the asset's price at fire time%alert_name%— the alert's name%alert_note%— your alert note text%price_action_event%—touch,break_through,bounce, orscript_returned_true
Strategy Bot webhooks
%bot_symbol%— the bot's symbol%bot_status%—in_positionornot_in_position%last_price%— current price%bot_name%,%bot_timeframe%
TrendSpider has no action or quantity variable. Direction is hardcoded
per alert (a "buy" alert sends "action":"buy", a "sell" alert sends
"action":"sell"), and quantity is hardcoded or omitted so Nyria's own bot
sizing decides.
Before you start
You need:
- A Nyria strategy whose alert source is TrendSpider.
- A connected broker on that strategy — see the per-broker pages under /integrations.
- A TrendSpider plan that includes webhook alerts (confirm the tier on TrendSpider's pricing page — outside Nyria's control).
Paper-trade the full loop before pointing a live broker at it. Webhook alerts execute orders without further confirmation.
Setup — Alerts (one strategy)
Copy your Nyria webhook URL
In Nyria, open the strategy → Integration tab → copy the webhook URL:
https://trades.nyria.io/webhooks/YOUR_STRATEGY_TOKENTreat the token like a password — anyone with the URL can submit alerts.
Set the account webhook URL in TrendSpider
TrendSpider sends all alert webhooks to one URL: User Icon → Account &
Settings → check the Webhook box → paste the Nyria URL. Method POST. (Because
this is account-wide, every alert you arm feeds this one Nyria strategy.)
Put the payload in the alert's note
TrendSpider uses each alert's description / note as the POST body. If it's
valid JSON, TrendSpider sends application/json. Paste:
{
"symbol": "%alert_symbol%",
"action": "buy",
"price": "%last_price%"
}Set "action" to "buy" on your entry alerts and "sell" on your exit alerts
(TrendSpider can't vary it for you). %alert_symbol% and %last_price% are
filled in live.
Test, then arm
Fire TrendSpider's Send Test Alert, watch the strategy's Logs tab in Nyria for the inbound payload and parsed order, then set the alert Active and make sure the Nyria strategy is Active with a bot attached.
Setup — Strategy Bots (route many strategies)
Each TrendSpider Strategy Bot has its own webhook URL and body, so point each bot at a different Nyria strategy token. In the bot's webhook body:
{
"symbol": "%bot_symbol%",
"action": "buy",
"price": "%last_price%"
}Configure the bot's entry webhook with "action":"buy" and its exit
webhook with "action":"sell" (TrendSpider lets you set a separate body per
event). %bot_symbol% gives Nyria the ticker dynamically — no per-ticker
hardcoding needed.
Options, limits, and multi-leg
The payload above covers single-leg stock and crypto market orders. Everything else uses the same fields as any other source — Nyria's parser is source-agnostic:
{
"symbol": "%alert_symbol%",
"action": "buy",
"order_type": "limit",
"price": "%last_price%"
}order_type—market,limit,stop, orstop_limit(defaultmarket).price— required for any non-market order;%last_price%is TrendSpider's last-trade price at fire time.- For options strikes, multi-leg spreads, and dollar-notional crypto, see /webhook-reference. If your strategy uses internal option selection, just send the directional alert above and Nyria builds the contract from your strike/delta/DTE config — same as TradingView or Discord.
How the values map inside Nyria
| TrendSpider variable | Webhook field | Where Nyria uses it |
|---|---|---|
%alert_symbol% / %bot_symbol% | symbol | Matched against the strategy's instrument filter, then routed/translated per broker (Schwab option roots, Binance BTCUSDT, etc.). |
| (hardcoded) | action | Interpreted via the strategy's Trading Behavior. buy/sell are canonical; entry/exit/open/close also accepted. |
%last_price% | price | Used for limit/stop orders; ignored for market orders. |
Troubleshooting
- 401 — wrong token in the URL. Re-copy it from the Integration tab.
- 200 with
skipped: true— strategy paused, or the symbol isn't on the strategy's instrument list. - 422 — malformed JSON, or a required field (e.g.
priceon a limit strategy) is missing; the body lists the offending fields. - Broker rejects the order — Nyria logged it but the broker said no; the broker's message is in the same log row (buying power, non-tradable instrument, outside market hours).
- All my alerts hit one strategy — that's the account-level alert URL. Use Strategy Bots (per-bot URLs) to fan out to multiple Nyria strategies.
What's next
- Webhook payload reference — every field, with options, multi-leg, and crypto examples.
- Alert sources overview — TradingView, Discord, and Custom API equivalents.
- Trading behavior — what
buy/sellmean inside a Nyria strategy and how exits pair to entries.
Stream Telegram channel alerts to Nyria
Add the Nyria Telegram bot to your channel, authorize Nyria to read it, and stream signal messages straight into your strategies.
Use a Custom Webhook Source
Wire any service that can POST HTTP to Nyria. By the end you will have a working custom webhook firing real orders through your connected broker.