Choose an alert source

Nyria reads trade alerts from TradingView, Discord, Telegram, TrendSpider and your own bot or script. Each strategy takes one source, and every source sends the same kind of alert: plain text, or JSON from TradingView, TrendSpider and your own bot. Options strategies can pick contracts from your rules on every source, and take them from the alert itself on every source but TradingView.

A strategy reads alerts from one source. TradingView, TrendSpider and custom webhooks post to a webhook URL that Nyria gives the strategy. For Discord and Telegram there is no URL: Nyria reads the channel or chat you pick.

Every alert needs a ticker, a direction and an action, like SPY long entry. Word your exits the same way as your entries, so Nyria can match them.

TradingView

Trade on alerts from a Pine strategy or an indicator on your TradingView chart. TradingView alert webhooks need a paid TradingView plan. An indicator needs one alert per condition on each ticker, so convert it to a strategy when you want a single alert to cover every entry and exit.

TradingView guide →

Setup

1. Create a strategy with TradingView as the alert source.
2. On its Integration tab, follow Create the alert and Check format.

Alert format

A TradingView alert can be plain text:

long entry spy

Or JSON:

{
  "ticker": "SPY",
  "action": "buy"
}

Or TradingView's default alert message for Pine strategies.

TradingView variables

TradingView replaces placeholders in double braces when the alert fires:

• {{ticker}}: the chart's ticker, like SPY
• {{close}}: the bar's close price
• {{time}}: the bar's open time, in UTC

Paste your alert message, placeholders included, into the Check format step on the strategy's Integration tab. Nyria fills in the placeholders and checks each alert type.

Options strategies

TradingView options strategies always use Contract selection: From my rules. Set the option selection rules on the strategy.

TradingView repainting warning

Fire alerts only on confirmed bars (barstate.isconfirmed), and read higher-timeframe data from the last closed bar (close[1]). Before you automate, watch the script live for two weeks and compare each alert with what the chart shows later.

TradingView's guide to repainting

TradingView webhook delays

TradingView decides when to send each alert, and some arrive late, sometimes by a minute. If a few seconds change your fill, don't trade sub-minute timeframes.

Discord

Trade on alerts posted in a Discord server you run.

Discord guide →

Setup

1. Link your Discord account on the Integrations page.
2. Invite the Nyria bot to a Discord server where you have Manage Server.
3. Create a strategy with Discord as the alert source.
4. Set:
   • Discord server: the server the Nyria bot is in
   • Discord channel: the channel to read
   • Author (optional): only messages whose poster's display name contains this text
   • Keyword (optional): messages containing this text only

Alert format

Nyria reads Discord alerts as plain text:

SPY long entry

Close short BTC

SPY 780C buy to open

For options set to Provided in alert, give the strikes:

SPY 780C/781C bull call spread

Expiration handling

With Provided in alert, a Discord or Telegram entry with no date takes the nearest listed expiration. That can be today's expiration (0DTE), even late in the day. An alert from any other source has to name the expiration.

Telegram

Trade on alerts posted in a Telegram group or channel you run.

Telegram guide →

Setup

1. Create a strategy with Telegram as the alert source.
2. Select Connect Telegram, press Start in the chat with @NyriaAlertsBot, then tap Link in its reply.
3. Add Nyria to a group or channel as an admin. You need to be the chat's owner, or an admin who can add admins.
4. Pick the chat, and optionally an author or keyword filter.

Alert format

Telegram alerts are plain text, in the same formats as Discord:

SPY long entry

Close short BTC

An edited message is not traded, and an alert that reaches Nyria more than a minute after it was posted places no new entry; a close in it still runs.

TrendSpider

TrendSpider posts alerts to the strategy's webhook URL, from a chart alert or a Strategy Bot. The TrendSpider setup guide shows when to use each.

Setup

1. Create a strategy with TrendSpider as the alert source.
2. Copy the webhook URL from the Integration tab.
3. In TrendSpider, set the alert webhook to that URL.
4. Format alerts the way you would for TradingView.

Use Contract selection: From my rules for options strategies.

Your own bot

Send alerts from your own code over HTTP: POST plain text or JSON to the strategy's webhook URL.

Custom webhook guide →

Setup

1. Create a strategy with Custom webhook as the alert source.
2. Copy the webhook URL from the Integration tab.
3. Send POST requests to the webhook URL.

Payload

Send JSON:

{
  "instrument": "SPY",
  "action": "OPEN",
  "direction": "LONG",
  "price": "771.20"
}

For options set to Provided in alert:

{
  "instrument": "SPY",
  "action": "OPEN",
  "direction": "LONG",
  "legs": [
    {
      "strike": 780,
      "side": "CALL",
      "expiration": "2026-11-20",
      "action": "buy_to_open"
    }
  ]
}

Authentication

The token in the webhook URL is the only authentication. Keep the URL private.

Rate limiting

If you send alerts faster than the webhook accepts them, it answers 429. Wait and retry, or space your alerts out. An identical alert repeated within 30 seconds, or within 5 minutes with no other alert in between, counts as a duplicate and is skipped. See handle the response.

Checking the alert format

A strategy goes Active once its alert format passes. On its Integration tab, give one example alert per trade type and select Check format. If one fails, see troubleshooting. To try a message before the strategy exists, paste it into the alert tester.

Next steps

• Create your first strategy
• Set trading behavior
• Alert format
• Webhook reference: every field Nyria accepts
• Discord copy trading and Telegram signals to your broker, on nyria.io