Skip to content
DiscordTwitter

Edges

Edges are the arrows connecting your boxes. They show how data moves from one node to another like pipes carrying water.

Edges

An edge is just a connection:

  • Start: From a dot on the right side of a node (output)
  • End: To a dot on the left side of another node (input)

When Market Ticker outputs a price, the arrow carries that number to RSI Indicator.

  1. Click a dot on the right side of a node
  2. Drag to a dot on the left side of another node
  3. Release — done!

The system won’t let you connect incompatible types. If it won’t connect, the data types don’t match.

Edges carry different types of data:

  • Numbers: 150.75 (stock price)
  • Text: "AAPL" (asset symbol)
  • True/False: true (price > 150?)
  • Objects: Complex data like full ticker info
Edge Status

Look at the arrow:

  • Animated dots: Data flowing RIGHT NOW!
  • Solid line: Connected, but idle
  • Red line: Error! Something’s wrong
  • Delete: Click the edge, press Delete
  • Reconnect: Click the arrow, drag the end to a different dot
  • See data: Click the edge to see what’s flowing (current value)
  • Configure: Click the circle on the edge to open the configuration dialog

Click the circle button on any edge to configure Filter and Transform options.

Edge Configuration

Filter expressions control which data passes through the edge. Only data that evaluates to true will continue.

Examples:

  • data > 100 — Only pass values greater than 100
  • data.price > 150 — Only pass when price field exceeds 150
  • data == "BUY" — Only pass when value equals “BUY”

Advanced filter options give you more control over when data is sent:

When enabled, data is only sent the first time the filter becomes true. The edge will not send again until the filter becomes false, then true again.

Use case: Alert me when RSI crosses above 70, but don’t spam me while it stays above 70.

How it works:

  1. Filter becomes true → Data passes through ✓
  2. Filter stays true → Data is blocked ✗
  3. Filter becomes false → State resets
  4. Filter becomes true again → Data passes through ✓

When “Send Once Per Trigger” is enabled, you can optionally set a time-based reset. After the specified seconds, the “sent” state resets automatically, even if the filter hasn’t become false.

Use case: Send a notification when price drops below $100, but allow another notification after 60 seconds even if price stays low.

Example: Set to 60 to allow sending again after 1 minute.

Transform expressions modify data before it reaches the next node. Useful for type conversion or data extraction.

Examples:

  • data * 2 — Double the value
  • data.close — Extract just the close price from a ticker object
  • string(data) — Convert number to text

One Market Ticker → Three RSI Indicators (different periods)

Same price data goes to multiple nodes. Perfect for testing different strategies!

Three Market Tickers (AAPL, GOOGL, TSLA) → One Synchronizer → One Telegram

Wait for ALL three prices, then send one alert.

Market TickerRSIAND ConditionMarket Order

Data flows left to right through each step.

AND Condition has two outputs: true and false

Connect true to Market Order (execute!)
Connect false to Telegram (just alert me)

Q: Why won’t my edge connect?
A: Data types don’t match. Check: is the output a number but the input expects text?

Q: My edge is red!
A: Click it to see the error. Usually means data stopped flowing or wrong type was sent.

Q: Can I see what’s flowing through an edge?
A: Yes! Click the edge to see the current value. Or add a Printer node to log everything.

Q: Can one output connect to multiple inputs?
A: Absolutely! One Market Ticker can feed five different indicators.

Arrange nodes so arrows flow left-to-right. Makes it easy to follow the logic!

Avoiding connecting output back to earlier inputs—it can create infinite loops and crash your flow.

Not sure what data looks like? Insert a Printer node anywhere to see everything flowing through.