Skip to documentation
Screebits Docs
Flow Editor
Open Screebits
  • Screebits
  • Flow Editor documentation
  • Blueprints
  • Your first steps in Screebits
  • Workspace, strategies and account
  • Get started with the Flow Editor
  • Build an RSI Momentum Alert
  • Flow Editor concepts
  • How a strategy starts and continues
  • Control and data connections
  • Nodes, parameters, outcomes, and ports
  • Plans and feature availability
  • Saves, versions, and checkpoints
  • Tactical and Portfolio strategies
  • Validation and readiness
  • Flow Editor mode guides
  • Build Portfolio strategies
  • Build Tactical strategies
  • Flow Editor guides
  • Add a Quant Hub metric
  • Configure a node
  • Configure Settings and visual preferences
  • Connect nodes
  • Create a strategy
  • Create checkpoints and restore versions
  • Reset a Flow safely
  • Debug and replay a Backtest
  • Fix validation issues
  • Use keyboard shortcuts
  • Manage variables
  • Run a Backtest
  • Save and resolve conflicts
  • Work on tablet and mobile
  • Use Quick add
  • Use the Inspector
  • Add, move, duplicate, and remove nodes
  • Flow Editor examples
  • Portfolio rebalance with risk limits
  • Tactical order and position monitoring
  • Use Backtest Center
  • Read a Backtest result
  • Compare and export Backtests
  • Explore Quant Hub
  • Metric parameters, charts and overlays
  • Flow Editor node reference
  • Alert
  • Flow Editor troubleshooting
  • Troubleshoot activation and validation
  • Troubleshoot Backtests and replay
  • Troubleshoot compact layouts
  • Troubleshoot connections and data types
  • Troubleshoot plans and locked features
  • Troubleshoot Quant Hub in the Flow Editor
  • Troubleshoot save, offline, and conflicts
  • Backtests and responsible use
  • Flow Editor glossary
  1. Screebits
  2. /Flow Editor documentation
  3. /Flow Editor node reference
  4. /Alert
IntermediateLast verified Sep 30, 2026

Alert

Records an Alert message on a control outcome; Backtests simulate delivery.

On this page
  1. When to use
  2. Example
  3. Make the message match the rule
  4. Common problems
  5. Next steps

Records an Alert message on a control outcome; Backtests simulate delivery.

When to use

Use it for a user-visible notification on a meaningful control outcome.

Example

On Condition Match, send a message that includes the symbol and indicator value.

Try it here

Explore Alert

Records an Alert message on a control outcome; Backtests simulate delivery.

Exercise steps
  1. Change Message source from Literal to Data port.
  2. Observe the required Message input, then return to Literal and edit the text. No email is sent.
Event TriggerAlert
Graph preview — a diagram of the example

Make the message match the rule

For the RSI Starter, connect Condition: Match to Alert, choose the literal message source, and write BTCUSD RSI is above 60. If you later raise the Condition threshold to 65, update the message too; the text does not automatically follow the comparison parameter. If you choose the data-port message source instead, connect a compatible string output to Message. A numeric Indicator output cannot be connected as message text without a supported conversion.

Alert's configured delivery target describes the product target, but a Backtest records a simulated Alert event and does not email the account. The node has a Next continuation; it does not prove that an Order was submitted or filled. When checking a run, inspect the event, the branch that reached Alert, and the actual message. Consecutive bars above a simple Greater-than threshold may produce repeated Match activations.

Common problems

Alert needs a control arrival. Keep messages clear and avoid assuming that an alert proves an order or rebalance succeeded.

Next steps

Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.

In a Backtest, the Account Email target produces a simulated event without sending an email. Saving the graph alone does not activate delivery.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Alert
Activation role
No activation role
Category
Action
Availability
Tactical and Portfolio
Modes
Tactical and Portfolio
Required plan
None
Behavior
Performs an action
Control inputs
1
Output data types
None

Parameters

NameInput typeRequirementDefaultOptions and constraints
Send toSelection listRequiredaccountEmailOptions: Account email
Message sourceSelection listRequireddataPortOptions: Message port, Literal
MessageLong textRequired when shownNot setMaximum: 512; Shown when Message source is literal

Primary parameters

  • Message source
  • Message

Outcomes

  • Next

Data inputs

  • MessageText · Required when shownShown when Message source is dataPort

Data outputs

None

Related documentation

  • String TemplateBuilds a readable message from a template and connected values.
  • Build an RSI Momentum AlertCreate the Starter strategy, change its threshold, validate it, save it, and reopen it.
  • Backtests and responsible useInterpret simulated results with appropriate limits and avoid treating them as predictions or advice.

On this page

1 / 5
  1. When to use
  2. Example
  3. Make the message match the rule
  4. Common problems
  5. Next steps

Practical guidance for strategies, historical simulations and metric research in Screebits.

Responsible useGlossary