# Notifications and company alerts

Send observed events to destinations connected to your own account.

Human page: https://docs.orbi.gg/guides/notifications

## Connect a destination first

Connect Telegram or Discord in Settings. Telegram uses your linked account; Discord lets you select one of your connected servers and an eligible text channel.

A graph config cannot smuggle in someone else’s account, an arbitrary destination or credentials. The graph remains invalid if a required Discord destination has not been selected.

## Attach an alert branch

Attach a notification to a successful source, filter, fill or exit trigger. Notifications are terminal side branches and do not need End. They do not replace an exit’s required sell/close action.

Choose the event fields you need. Missing fields are omitted. Wallet amount describes the watched wallet; My entry describes the bot’s confirmed fill. These are not interchangeable.

[Telegram notification](https://docs.orbi.gg/nodes/telegram-notify)

[Discord notification](https://docs.orbi.gg/nodes/discord-notify)

## Build a company-movement graph

Tier 1 company sources can send SEC reports or company news to notifications without wallets, Balance or Open trade. Use the covered Nasdaq-100 universe or explicitly covered tickers.

The example below is an alert-only graph. A company headline does not become a crypto order.

### Company reports to Telegram

A Tier 1 notification-only graph. Connect your Telegram account; no trading funds or order nodes are needed.

- Start → SEC reports

- SEC reports → Telegram notification

- Telegram notification → terminal

## Relevance is not a forecast

Important filters medium/high relevance and excludes routine-only 8-K filings. High only can exclude medium-classified quarterly and annual reports.

Alerts require a configured, healthy collector. Only newly collected events meeting freshness rules are delivered; a historical backfill should not arrive as a new live alert. No alert is a promise of market movement.