Trade alerts from a Discord server you run

Add the Nyria bot to a Discord server you run, pick the channel, and each alert posted there becomes an order at your broker. The bot reads the ticker, the direction and the action from the message's embeds or its text. Threads, DMs and later edits are not read.

Nyria turns the options and stock alerts posted in a Discord channel into orders at your broker. Members of a server someone else runs can't connect it themselves: they subscribe to the strategy its owner publishes on Nyria. You check the reading on real messages before any bot is deployed. This page is the reference. For the short version, see how to turn Discord options alerts into broker orders, or Discord options alerts to broker orders on nyria.io. Paper is free. Live trading from $15 a month.

Before you start

You need:

• A Nyria account with at least one connected broker. See Integrations.
• Manage Server permission in the Discord server you want to read from.
• The ID or name of the channel where the alerts are posted.

Without admin access to the server, send the alerts through TradingView or your own bot instead. See the webhook reference for the payload.

Steps

How Nyria reads Discord messages

Nyria reads three things from each Discord message, in this order:

1. Embeds, if the message has any.
2. Quoted tweet, if the message is a Twitter/X link that Discord unfurls.
3. Free text, the message body itself.

The first one that gives a ticker, a direction and an action is used, and the rest are ignored for that message.

Embeds

When a bot, webhook or Discord app posts a message with a rich embed, Nyria reads the embed in this order:

1. embed.title
2. embed.description
3. each embed.fields[i].name + embed.fields[i].value joined by a space

Nyria reads each piece the way it reads free text, and uses the first piece it can read.

Example. A TradingView Discord webhook payload posts this embed:

{
  "embeds": [
    {
      "title": "SPY long entry",
      "description": "Trigger: 20EMA cross",
      "fields": [
        { "name": "Strike", "value": "780C" },
        { "name": "Risk", "value": "1R" }
      ]
    }
  ]
}

Nyria reads SPY long entry from title and finds 780C in the fields, so each of the strategy's bots buys the SPY 780C. The other fields are ignored.

Free text

If the message has no embeds, or Nyria can't read any embed piece, it reads the message body. This is the usual case for callers who type alerts by hand.

Free text takes the same shapes as plain-text TradingView alerts:

SPY long entry

Close short BTC

AAPL 345C buy to open

sold half SPY 780C

Nyria ignores case, trailing punctuation, emoji, and @everyone or @here mentions. It doesn't guess at questions or hedged wording: thinking about SPY? places nothing.

Quoted tweets (longed / shorted)

When someone pastes a Twitter/X link, Discord unfurls the tweet as an embed with embed.description = tweet text and embed.author.name = @handle. Nyria handles this case separately, for the common "I longed it" and "I shorted it" calls.

For a quoted-tweet embed, Nyria also reads:

• longed <SYMBOL> → long entry
• shorted <SYMBOL> → short entry
• closed long <SYMBOL> → long exit
• closed short <SYMBOL> → short exit

Example tweet content:

longed NVDA at 224.40, stop 221

Pasted into the authorized channel, this places an NVDA long entry. The price (224.40) and stop (221) are read as metadata, and Nyria places no stop order: the position closes on the caller's later exit alert.

Author filter

The Author (optional) filter matches the poster's display name in the server, ignoring case, and part of a name counts: trader matches TraderJoe. It compares names, so a user ID never matches.

A display name can change. If a caller renames themselves, update the filter. Anyone in the server can take a matching display name, so the filter narrows a channel but doesn't lock it: use a channel only the caller can post in. If a caller posts the same alert from a personal account and a server bot, use the bot's name.

Keyword filter

Use the keyword filter when the alerts channel also has chatter:

The filter matches the keyword anywhere in the message, ignoring case. A keyword of entry matches Long entry SPY and Entry: AAPL but not analysis.

Discord quirks

Edits and deletes do nothing

After Nyria trades on a message, editing or deleting the message doesn't reverse, change or cancel the order. Nyria acts on the message as first posted and doesn't watch for edits or deletions. To get out of the position, post a normal exit alert.

Forwarded messages aren't read

Nyria doesn't read a message shared with Discord's Forward feature. Post the alert in the channel itself.

Rate-limited reconnects

Discord's gateway throttles bot reconnects per server. During a Discord outage, the bot can miss up to about 30 seconds of messages while it reconnects. Missed messages are not replayed: an alert posted in that window is lost.

Attachments are ignored

Nyria doesn't read text in images, videos or files, such as a chart screenshot with "long SPY" written on it. The caller has to type the alert or post an embed.

@everyone and role pings

Mentions are removed first, so @everyone long SPY reads the same as long SPY. The author filter still applies, and a user it does not name cannot get past it by pinging @everyone.

Troubleshooting

Can't pick the server

You need Manage Server permission in that server, and the Nyria bot has to be in it. Invite the bot again with Invite bot to server (or Add server) in the strategy's Discord channel step, and check your roles in the server's Server Settings → Members.

"Pick a text channel the Nyria bot can see"

The channel was deleted, turned into a voice, forum or stage channel, or a channel override took away the bot's View Channel permission. Open the channel's permissions in Discord, give the Nyria role View Channels, then pick the channel again under Discord channel in the strategy's Discord channel step.

Nyria couldn't read the alert

Nyria got the message, but no embed piece, quoted tweet or free-text shape matched. Open the message on the strategy's Alert format card to see which sources Nyria tried and why each failed. Common fixes:

• The caller wrote "added more SPY", which implies a direction without stating it. Ask for "added long SPY".
• The caller posted only a chart image. See "Attachments are ignored" above.
• The embed put the symbol in embed.footer, which Nyria doesn't read. Move the symbol to the title, description or fields.

Paste the message into the alert tester to see which shape it would match, or the refusal it would get.

The webhook reads alert text the same way. See the webhook reference.

Trades fire on the wrong account

The bot, not the strategy, picks the broker account. Open the strategy's My bots tab and check the active bot trades the account you meant.

Multiple entries disabled

The strategy allows one open position at a time, and one is open. Close it by posting the matching exit alert in the channel, or turn on Allow multiple entries on the strategy.

Questions

Which permission does the Nyria bot need?

One: View Channels. The bot reads the channel and never posts in it.

Can one strategy read two channels?

No. One channel per strategy. A caller who posts in two channels needs two strategies.

What if a caller edits or deletes a message?

Nothing changes. After Nyria trades on a message, editing or deleting it doesn't reverse, change or cancel the order. Post an exit alert to close the position.

Can I connect a Discord server I don't run?

No. You need Manage Server permission to invite the bot. If the owner publishes the calls as a Nyria strategy, subscribe to it and deploy it on your own account.

What does it cost?

Paper is free. Live trading from $15 a month, priced by your total entry allocation.

Related

• How to turn Discord options alerts into broker orders: the step-by-step guide.
• Discord options alerts to broker orders, on nyria.io: the same setup for the server owner and for members.
• If you run an alert service, sell access to your strategy. Each member runs a bot on it in their own brokerage account.
• Link your Discord account: permissions, security and account linking.
• Webhook reference: send the same alert text in an HTTP request.
• What you can trade: the stock, option and crypto alerts Nyria reads.
• Trading behavior: how entries, exits and multiple entries work once an alert reaches the bot.