# Discord notification

Tier 1 notification branch. Choose one of your connected Discord servers, a text channel, an embed accent and the event fields to send. No End connection is needed.

Node ID: `discord-notify` · Category: Notifications · Minimum plan: Tier 1 and above

Human page: https://docs.orbi.gg/nodes/discord-notify

## How it works

Choose one of your connected servers and a text channel, then select an embed colour and event fields.

Attach it to a successful company event, candidate, fill or exit trigger. Trading links and the optional token image use the observed event data.

## Settings

| Setting | Config key | Initial value | Details |
| --- | --- | --- | --- |
| Connected server | `guildId` | Choose in the app | Choose a server connected to your account; there is no default destination. |
| Text channel | `channelId` | Choose in the app | Choose an eligible channel in that connected server. |
| Embed colour | `colour` | purple | Purple, blue, green, red, orange, yellow or white. |
| Message fields | `fields` | 17 fields selected | Choose at least one field: Bot + event, Token name, Token address, Trading links, 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, Token image. |

### Stored defaults

```json
{
  "colour": "purple",
  "fields": [
    "event",
    "token",
    "token-image",
    "token-address",
    "wallet-address",
    "market-cap",
    "price",
    "pnl",
    "reason",
    "jupiter-link",
    "company",
    "headline",
    "filing",
    "importance",
    "summary",
    "source-link",
    "publication-time"
  ]
}
```

## 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: [SEC reports](https://docs.orbi.gg/nodes/sec-filings), [Company news](https://docs.orbi.gg/nodes/company-news), [Aegis wallet feed](https://docs.orbi.gg/nodes/aegis-wallet-feed), [Wallet signal](https://docs.orbi.gg/nodes/wallet-signal), [Wallet confirmation](https://docs.orbi.gg/nodes/wallet-confirmation), [Wallet conviction](https://docs.orbi.gg/nodes/wallet-conviction), [Runner potential](https://docs.orbi.gg/nodes/runner-potential), [Twitter traction](https://docs.orbi.gg/nodes/twitter-traction), [Token filter](https://docs.orbi.gg/nodes/token-filter), [Entry chase](https://docs.orbi.gg/nodes/entry-chase), [Demand confirmation](https://docs.orbi.gg/nodes/demand-confirmation), [Setup failed](https://docs.orbi.gg/nodes/setup-failed), [Open trade](https://docs.orbi.gg/nodes/open-trade), [Profit target](https://docs.orbi.gg/nodes/profit-target), [Stop loss](https://docs.orbi.gg/nodes/stop-loss), [Trailing stop](https://docs.orbi.gg/nodes/trailing-stop), [Time exit](https://docs.orbi.gg/nodes/time-exit), [Sell position](https://docs.orbi.gg/nodes/sell-position), [Close trade](https://docs.orbi.gg/nodes/close-trade)

Connects to: [End](https://docs.orbi.gg/nodes/end)

## Before you run

- Requires Tier 1. Terminal alert branch; no End connection is required. A connected server/channel must be selected before the graph is valid.

- Destinations are account-owned and unsuccessful branches cannot masquerade as successful alerts.

- An End connection is accepted for legacy graphs, but is not required for notification delivery.

[Full graph rules](https://docs.orbi.gg/guides/graphs) · [Paper assumptions](https://docs.orbi.gg/guides/paper-trading)