# Getting started with custom notifications

> Get told when a global matches your rules. Set up a notification once and it watches every global for you, then sends it to Discord or to your own endpoint.

Source: https://www.entropiacentral.com/documentation/custom-notifications/getting-started
Last updated: 2026-07-29

---

A custom notification watches globals as they are recorded and sends you the ones you care about. Societies use them for a feed of member globals, hunters use them to catch their own big returns, and developers use them to pipe live data into their own tools.

You manage them under **Custom notifications** in your dashboard.

Every notification has three parts:

1. **A name**, so you can find it later.
2. **Conditions**, which decide when it fires.
3. **A destination**, either a Discord channel or your own webhook endpoint.

## Creating one

Open **Custom notifications** and choose **New notification**.

**Step 1, name and type.** Give it a name only you will see, then pick where it should go. [Discord](https://www.entropiacentral.com/documentation/custom-notifications/discord-webhooks) posts a formatted message into a channel. [Webhook](https://www.entropiacentral.com/documentation/custom-notifications/webhook-notifications) sends signed JSON to a URL you control. The type cannot be changed after the notification is created, so if you need both, create two.

**Step 2, when it fires.** Set your filters. Every filter is optional, and leaving one empty means it matches everything.

**Step 3, where it goes.** Paste your destination URL and use **Send test event** to confirm it works before saving. The test sends a sample global, so you see a real message land rather than waiting for one to happen.

**Step 4, message.** Discord only. Keep the recommended format or write your own.

A live summary of your rules sits beside the form and reads back what you built as a sentence, for example *"Notifies when the value is at least 500 PED and the type is any of Hunting"*. Check that sentence before saving. It is the quickest way to catch a filter that says something other than what you meant.

You can switch a notification off later without deleting it.

## Filters

The simple editor covers what most people need:

| Filter | What it does |
| --- | --- |
| Event types | Hunting, Mining, Space Mining, Construction, Discovery, Rare Item, Tiered Item, PvP |
| Minimum value | Only globals at or above this many PED |
| Rarity | Everything, HOF only, or ATH only |
| Team or solo | Team globals, solo globals, or both |
| Avatars | Only globals from the avatars you list |
| Society | Only globals from members of your society |
| Creatures | Hunting globals for the creatures you list |
| Land areas | Only globals from the land areas you list |

Avatars, creatures and land areas take several entries separated by commas.

Two things worth knowing:

- **PvP globals carry no PED value**, so the minimum value filter switches itself off when PvP is the only type selected.
- **Society filtering needs you to be in a society.** If you are not, the notification never matches anything.

## Advanced conditions

Switch to **Advanced** for anything the simple filters do not cover: item names, tier levels, PvP kill sprees, timestamps, `contains` and `starts with` matching, `OR` logic and nested groups.

Rules combine with **Match all** (`AND`) or **Match any** (`OR`), and groups can be nested. The limits are **5 conditions per group** and **5 levels of nesting**, which is enough for anything reasonable while stopping a runaway rule set.

Switching from Simple to Advanced carries your filters across, so nothing is lost. Going back is not automatic though: once you build something the simple editor cannot express, the notification stays in Advanced.

### Fields you can match on

| Field | Type | Operators |
| --- | --- | --- |
| `GlobalValue` | number | `=` `!=` `>` `<` `>=` `<=` |
| `TieredItemTier` | number | `=` `!=` `>` `<` `>=` `<=` |
| `PvpSpree` | number | `=` `!=` `>` `<` `>=` `<=` |
| `Type` | string | `=` `!=` `IN` `NOT_IN` |
| `AvatarName` | string | `=` `!=` `IN` `NOT_IN` `CONTAINS` `STARTS_WITH` `ENDS_WITH` |
| `CreatureName`, `DepositName`, `LandareaName`, `CraftedItemName`, `RareItemName`, `DiscoveredItemName`, `TieredItemName` | string | `=` `!=` `IN` `NOT_IN` `CONTAINS` |
| `IsHof`, `IsAth`, `IsTeam` | boolean | `=` |
| `IsSocietyMember` | boolean | `=` |
| `DateTime` | datetime | `=` `!=` `>` `<` `>=` `<=` |

`Type` accepts Hunting, Mining, Space Mining, Construction, Discovery, Rare Item, Tiered Item and PvP.

`IsSocietyMember` is what actually restricts a notification to your society. The society toggle in the simple editor adds this rule for you. In Advanced you need to add it yourself.

## Getting the volume right

The usual mistake is a notification that is too broad. Globals happen constantly, and a rule like "value above 50" will bury a channel and get it muted within a day.

Some starting points that work:

- **Society feed:** society members only, plus a minimum value that suits how active your society is.
- **Personal alerts:** your own avatar name, no value filter, so you get everything you land.
- **Records only:** rarity set to HOF only, or a high minimum value.
- **One creature:** the creature you are hunting, with a value floor to skip the small returns.

Start narrower than you think you want and widen it. A quiet channel people still read beats a busy one everybody has muted.

## Checking delivery

Each notification card shows how many events were sent and how many failed in the last 24 hours, along with the most recent attempt and the error if it failed. **Test** re-sends a sample event at any time.

If a notification stops arriving, check in this order:

1. It is still switched on.
2. The destination still exists. Deleting a Discord channel or webhook breaks it silently, and so does taking your own endpoint offline.
3. Your conditions still match something. A condition on a creature or item name that was later corrected in the wiki can stop matching with no visible error.