Telegram notification
Ends a notification branch; no End connection is needed. Choose the colour and fields sent to your connected Telegram account. Wallet amount is the watched wallet's trade; My entry is your bot's filled amount, excluding separate fees and rent. Missing fields are omitted. Trade-action alerts wait for confirmed fills.
Node ID telegram-notifyMarkdown
How it works
Send selected event fields to the Telegram account connected in your own Orbi settings.
Choose a colour marker and fields. Wallet amount is the watched wallet’s trade; My entry is your bot’s filled amount, excluding separate fees and rent.
Settings
Initial values for a new node, not your saved graph. Existing graphs can have different settings.
| Setting | Initial value | Details |
|---|---|---|
Message colourmarker | None | Optional colour marker; None is the legacy default. |
Message fieldsfields | 16 fields selected | Choose at least one field: Bot + event, Token name, Token address, Jupiter link, Wallet address, Wallet amount · SOL, My entry · SOL, My entry · USD, Market cap, Token price, Net P&L, Exit reason, Runner stage, Time · UTC, Company ticker, Headline, Report + items, Importance + bias, Summary, Source link, Published · UTC. |
Connections
These lists show compatible node types, not approval of every graph. Branch, position context, subscription, no-cycle and complete-exit rules also apply. A node cannot connect to itself.
Accepts from
Connects to
Before you run
- Terminal alert branch; no End connection is required. Missing fields are omitted and trade-action alerts wait for confirmed fills.
- Recipients cannot be inserted as arbitrary graph credentials. Alerts attach to successful events, not no/fail/failed branches.
- An End connection is accepted for legacy graphs, but is not required for notification delivery.