Alerts

When a scanner rule’s conditions match, its Alert action creates an alert. The alert is delivered through the channels enabled in your user preferences at Settings > Alerts (/settings/alerts), and rule-level trigger limits control how often that action can fire.

You can enable multiple channels at once. Channel preferences apply across scanners and other alert sources, while each rule keeps its own trigger limit.

Alert channels

Webhook

Webhooks send a JSON payload to any URL you specify whenever an alert fires. This is the most flexible channel – you can connect it to custom dashboards, automation platforms, trading journals, or any service that accepts HTTP requests.

How to set up:

1. Open Settings > Alerts (/settings/alerts) and enable Webhook.
2. Enter your HTTPS destination URL and, optionally, a webhook secret for HMAC signature verification.
3. Save your alert preferences.

Scanner Alert actions send a JSON payload with alert details such as the instrument, rule, message, price, and timestamp.

Tip

Webhooks are perfect for building custom workflows. For example, you could send scanner alerts to a Google Sheet, a Notion database, or a custom Telegram bot – anything that can receive an HTTP POST request.

Discord

Post alerts directly to a Discord channel. This is popular with trading communities and groups who want to share scanner results in real time.

How to set up:

1. In your Discord server, go to Server Settings > Integrations > Webhooks and create a new webhook for the channel you want to use.
2. Copy the webhook URL.
3. Open Settings > Alerts (/settings/alerts) and enable Discord.
4. Paste the Discord webhook URL and save your alert preferences.

Alerts will appear as formatted messages in your chosen Discord channel, showing the instrument, the conditions that were met, and the current price.

Slack

Send alerts to a Slack channel through an incoming webhook. Works well for teams or traders who already use Slack as a daily communication tool.

How to set up:

1. In your Slack workspace, go to Apps > Incoming Webhooks (or create one via the Slack API) and generate a webhook URL for your chosen channel.
2. Copy the webhook URL.
3. Open Settings > Alerts (/settings/alerts) and enable Slack.
4. Paste the Slack webhook URL and save your alert preferences.

Slack alerts include the instrument name, matched criteria, price, and timestamp, formatted for easy reading.

Email

Receive alerts in your email inbox. Best for lower-frequency scanners (HOURLY or DAILY) or as a backup channel for important alerts.

How to set up:

1. Open Settings > Alerts (/settings/alerts) and enable Email.
2. Confirm that your Stratifyre account email is current, then save your alert preferences.

Note

Email delivery depends on your email provider and may take a few seconds to arrive. For time-sensitive alerts, pair email with a faster channel like Discord or Slack.

SMS

Receive a text message on your phone when an alert fires. This is the most immediate channel for traders who are away from their computer.

How to set up:

1. Open Settings > Alerts (/settings/alerts) and enable SMS.
2. Confirm that your Stratifyre account phone number is current, then save your alert preferences.

SMS alerts are concise by nature. They include the instrument, a brief description of the matched condition, and the current price.

Caution

SMS alerts are subject to carrier delivery times and may incur messaging charges depending on your mobile plan. Because channel preferences are global, enable SMS only when you want it available for your alert sources, and use rule trigger limits to control frequency.

Push

Push notifications appear in a registered browser or mobile device.

How to set up:

1. Open Settings > Alerts (/settings/alerts) and enable Push.
2. Select Subscribe to Push Notifications, allow the browser permission, and save your alert preferences.

Push delivery depends on the device subscription remaining active.

Rule cooldown periods

A cooldown period is the minimum time that must pass after a specific rule fires for an instrument before that same rule can trigger again. Each rule has its own limit, so one rule’s cooldown does not consume another rule’s allowance for the instrument. Cooldowns are essential for preventing alert spam when an instrument hovers around a trigger level.

Example: Imagine a scanner rule that alerts when RSI crosses below 30. Without a cooldown, if an instrument’s RSI fluctuates around 30, you could receive dozens of alerts per minute. With a 15-minute Once per period, that rule can alert once and then remains quiet for 15 minutes before it can fire again.

Setting a rule trigger limit

1. Open the rule definition used by your scanner.
2. Set Trigger to Once per.
3. Choose a period such as 5m, 1h, or 1D, then save the rule.

The Once per limit applies to that rule’s actions, including its Alert action. Once fires only once for the scanner’s lifecycle; No limit allows every matching evaluation.

Recommended cooldowns

Scanner Frequency	Suggested Cooldown
TICK	1 - 5 minutes
SECOND	1 - 5 minutes
MINUTE	3 - 15 minutes
5 / 10 / 15 MINUTE	15 - 60 minutes
30 MINUTE	1 - 4 hours
HOURLY	2 - 8 hours
DAILY	Usually not needed

Tip

Think of cooldowns from the perspective of how quickly you can act. If it takes you 10 minutes to evaluate an alert and decide whether to trade, set a cooldown of at least 10 minutes so you are not distracted by repeat alerts while you are still reviewing the first one.

Rate limiting

In Settings > Alerts (/settings/alerts), Minimum seconds between alerts adds a user-level spacing rule across enabled channels. Use it with each rule’s trigger limit when you need additional protection from a busy scanner or several scanners firing together.

Distance metrics

Distance metrics tell you how close an instrument is to triggering your scanner, even before it actually fires an alert. Think of it as a “proximity gauge” for each instrument in your watchlist.

How distance works

For every instrument in your scanner, Stratifyre calculates how far the current values are from meeting your criteria. This is expressed as a percentage or absolute distance, depending on the condition type.

Example: If your scanner triggers when RSI crosses below 30 and an instrument’s current RSI is 33, the distance metric would show that the instrument is 3 points away from triggering.

Using distance metrics

Distance metrics are visible on the scanner dashboard. They help you:

• Anticipate alerts – See which instruments are approaching your trigger levels before they actually fire.
• Prioritize attention – Focus on instruments that are closest to triggering rather than waiting passively for an alert.
• Fine-tune criteria – If many instruments are consistently close but rarely trigger, you might loosen your criteria slightly. If too many instruments trigger at once, you might tighten them.

Best practices

• Use multiple channels for important scanners. For example, send alerts to both Discord (for real-time awareness) and email (for a permanent record) in Settings > Alerts (/settings/alerts).
• Match rule trigger limits to your trading pace. If you trade on 15-minute charts, a 5-minute Once per period is a useful starting point. If you review setups once per hour, set a longer period.
• Start with fewer instruments and widen later. It is easier to evaluate alert quality with a focused watchlist. Once you are confident in your criteria, expand to larger baskets.
• Save channel preferences before going live. Confirm your webhook URLs, Discord or Slack destinations, account email and phone number, and Push subscription in Settings > Alerts (/settings/alerts).
• Review alert history regularly. Stratifyre logs every alert that fires. Periodically review your alert history to spot patterns, identify false signals, and refine your scanner criteria.