Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.stratalerts.com/llms.txt

Use this file to discover all available pages before exploring further.

The StratAlerts Discord integration brings scanner data into your guild as slash commands. Once you link a Discord account from your profile, you can pull watchlists, gappers, movers, and the upcoming economic calendar without leaving Discord — and the same /snooze controls available on the web and Telegram are available from any channel where the bot is installed.

​
Linking your Discord account

1

Open My Profile

From the StratAlerts sidebar, open My Profile. The profile page exposes connection cards for Pushover, Telegram, and Discord.
2

Connect Discord

Click Connect Discord to start the OAuth handshake. Discord prompts you to authorize the StratAlerts bot for the requested scopes. Approve to return to the profile page with the link confirmed.
3

Confirm the connection

The Discord card on My Profile updates to show your connected Discord username. From this point on, slash commands run from any guild that has the StratAlerts bot installed will recognize you as a linked user.

​
Slash commands for linked users

The following slash commands are available to any linked user in a guild where the StratAlerts bot is installed.
Returns a compact Markdown card listing your StratAlerts watchlists. Selecting a watchlist from the picker renders a monospace ticker table for easy scanning. You can also add tickers to an existing watchlist through an ephemeral picker and modal flow without leaving Discord.
Returns separate green and red embed cards for the top gap-up and gap-down equities. The data comes from the same Mission Control Top Gappers panel feed, with a default top-10 rows per side.
Returns separate green and red embed cards for top gainers and decliners. Defaults to stocks, with an optional market argument that accepts stocks, crypto, or futures. Gainers and decliners are filtered by sign before rendering, so positive movers never appear in the red decliners card.
/movers
/movers market:crypto
Returns a neutral embed card with this week’s earnings calendar. Without a ticker, it defaults to importance >= 5. With a ticker argument, it filters the week to that symbol.
/earnings
/earnings ticker:NVDA
The card folds BMO and AMC indicators into the date column to keep tables readable.
Mirrors the Telegram and web snooze controls. Choose a duration (15m, 4h, forever, or resume) and optionally restrict the snooze to specific scopes — setups, metrics, or simbreaks.
/snooze duration:15m
/snooze duration:4h scope:metrics
/snooze duration:resume
Snoozes pause push delivery without changing your saved alert groups, and resume clears the snooze immediately.
Returns an ephemeral list of available bot commands, arguments, and short descriptions. Use it as an in-Discord cheat sheet for the rest of the slash command surface.

​
Setup alert embeds

When a setup-alert delivery is configured for a guild channel, embeds use a compact format optimized for Discord:
  • The setup notation, direction, and timeframe appear in the title — the timeframe is wrapped in square brackets and separated by a bullet.
  • The body leads with the last price and the trigger time.
  • The footer renders timeframe-first TFC chips without a TFC label.
  • High-priority FinancialJuice news embeds use a red accent color, omit the duplicate top label, and keep headline text unlinked.
Trigger-time TFC snapshots prefer live current colors over stale persisted state, so the chip colors match what you see on the chart at the moment of the alert.

​
Staff-only commands

The following commands are restricted to staff. They expose operator-grade visibility into the scanner pipeline directly from Discord.
CommandDescription
/newsLatest headline cards from the FinancialJuice and operator news streams.
/simbreaksRecent simultaneous-break events from the index futures detector.
/calendarUpcoming USD economic events through the end of the current week, with the impact column included.
/alerts_statusCurrent alert pipeline health, including stream cursors and worker heartbeat ages. Stale labels are suppressed during quiet off-hours.
/alerts_replayReplay recent alert deliveries for a given symbol, timeframe, or window.
/discord_healthIntegration health for the Discord bot itself — guild count, command sync state, and last interaction.
/user_linkInspects a linked user’s Stripe subscription status, broader app access, and beta-tester flag.
/setups ticker:<symbol>Public embed card with the ticker’s active setup rows across timeframes, sorted by timeframe and paired with a compact TFC summary. The card uses a narrower table that drops C2 and continuation columns to reduce wrapping.
/watch ticker:<symbol>Toggles a channel-level realtime setup-alert watch on the symbol. Accepts a single ticker, CSV tickers, or off to clear the watch. Matching alerts are delivered back to the channel where the command was run.
Table-heavy commands (/setups, /news, /simbreaks, /calendar, /earnings, /alerts_status, and /alerts_replay) render as plain fenced text instead of embed cards, giving the output more usable width before wrapping.

​
FinancialJuice bridge

Operators can run a Compose-managed bridge that streams live FinancialJuice SignalR widget headlines and forwards high-priority, breaking, urgent, or active-critical alerts into a configured Discord channel. The bridge persists dedupe state and exposes admin-visible delivery status so failures are debuggable without console access.
The FinancialJuice Discord bridge is an opt-in operator integration. Reach out through Feedback if you want it enabled for your guild.

​
Troubleshooting

  • Commands do not appear in the guild. Ask staff to run the guild-scoped sync — slash commands are registered per guild and require an explicit sync after the bot is added.
  • /movers shows fewer rows than expected. Default is top 10 per side; the bot filters by sign so a market with few negative names will produce a shorter decliners card.
  • Account linking fails with a 403. The bot sends an explicit Discord API user agent, but corporate proxies can still strip headers. Retry from a network without proxy interception.