Notifications
MyHold App notifications let you create intelligent, rule-based alerts for your crypto portfolio. Instead of generic price alerts, you can build conditions based on your specific holdings—your entry price, wallet allocations, portfolio performance, and market insights.
✅ Try it live
MCP Tools#
AI agents can interact with Notifications through the MyHold MCP server:
| Tool | Description |
|---|---|
list-notifications | List all notification rules for the authenticated user. |
get-notification | Get a single notification rule by ID. |
create-notification | Create a new price alert or portfolio notification rule. |
update-notification | Update name, description, channels, active state, or execution policy. |
delete-notification | Delete a notification rule by ID. |
get-notification-logs | Get trigger logs for a specific notification rule. |
list-notification-logs | List all notification logs, optionally filtered by rule or unread status. |
get-notification-current-context | Get live variable values and whether a rule is currently satisfied. |
mark-notification-log-read | Mark a specific log entry as read. |
Notification Levels#
Each notification operates at a specific level that determines what it monitors:
| Scope | What it monitors | Example Use Case |
|---|---|---|
| Global | Market conditions | Alert when the Crypto Market is in "Extreme Fear" |
| Portfolio | Total value of your portfolio | Alert when my total portfolio value drops below $10,000 |
| Wallet | Specific wallets in your portfolio | Alert when my "DeFi" wallet becomes too large relative to my target |
| Coin | Individual coins you hold | Alert when Bitcoin drops below my average buy price |
How it works
When you set a notification to the **Coin** level, the system checks every coin you own. If any coin matches your rule (e.g., “Profit >10%”), you will receive an alert for that specific coin.
Live examples
Below are real notification cards rendered with different levels. These are the same components used in the app.
Portfolio-level notification — triggers per portfolio
Wallet-level notification — triggers per wallet
WalletCoin-level notification — triggers per coin
Creating Rules#
You can build rules using our visual builder. Combine conditions just like you would in a spreadsheet or smart filter.
Operators#
| Category | Examples |
|---|---|
| Comparison | Greater than (>), Less than (<), Equals (==) |
| Logical | AND, OR, NOT |
| Math | Add (+), Subtract (-), Multiply (*), Divide (/) |
Example Rules
Here are some examples of what you can create:
- Price Alert: Bitcoin Price > $100,000
- Profit Taking: My Profit > 20%
- Crash Warning: 24h Change < -10% AND Volume > 10M
Advanced Logic
You can combine multiple conditions to create precise alerts.
Portfolio Value > 10000 AND ( 24h Drop > 5% OR 7d Drop > 10% )Complex notification with nested AND/OR rule
✅ Real-world example: BTC Buy Signal
BTC Buy Signal — multi-indicator notification using RSI, StochRSI, and Fear & Greed
Execution Policies#
The execution policy controls when a notification is sent after the rule evaluates to true. This prevents alert fatigue and gives you control over notification frequency.
| Policy | Behavior | Best For |
|---|---|---|
always | Send every time the rule is true (on each evaluation cycle) | Critical real-time monitoring where you need constant updates |
once | Send only the first time the rule is ever true, then never again | One-time milestones (e.g., "portfolio reached $100k") |
on-reset | Send only when the rule transitions from false → true. Resets when the condition becomes false again. | Price crossing thresholds, avoiding repeated alerts while condition holds |
interval | Send at most once per configured interval (e.g., every 60 minutes) while the rule is true. | Periodic reminders during extended conditions |
💡 Recommended policy
Notification Channels#
Choose how you receive alerts. Each notification can deliver through multiple channels simultaneously.
| Channel | Availability | Description |
|---|---|---|
| 🔔 In-App | All Plans | Shows in your dashboard notification bell with unread indicators |
All Plans | Detailed notification delivered to your registered email | |
| 📲 Push | All Plans | Instant mobile push notification — alerts you even when the app is closed |
Coming Soon | WhatsApp messages for convenient mobile alerts |
Editing Notifications#
You can update a notification's name, description, delivery channels, active state, and execution policy at any time.
💡 Rule and level are immutable
rule and level of a notification cannot be changed after creation. Each log entry stores a snapshot of the variable values that triggered the alert under the original rule — changing the rule retroactively would make those historical logs ambiguous. To use a different rule or level, delete the notification and create a new one.Understanding Trigger Context#
When a notification fires, MyHold records the exact context data that caused it to trigger. This lets you inspect the values that were evaluated at the moment of the alert.
Notification conditions as displayed in the log history
Only the variables referenced in your rule are captured—this keeps logs compact and relevant. Note that all referenced variables are recorded, not just the one whose condition was satisfied. For example, in an OR rule with two conditions, both variable values appear in the context even if only one branch was true. For a full reference of all available context fields, see the Context Reference.
Next Steps#
Context Reference →
Full list of all available context fields for each notification level.
Try the Builder →
Interactive notification builder with live preview—no sign-up required.