02 · Alerts
Level and liquidation alerts
Alerts when price tags levels you wrote down, or when an estimated liquidation cluster you care about is close enough to matter.
- Level
- Starter
- Cadence
- Levels reviewed each session; alerts run while the session or the swing is live
- Read
- 7 min
- Updated
Definition
A level alert is a notification tied to a price you chose and a reason you wrote. A liquidation alert is the same idea applied to an estimated cluster from a data source you name. Neither alert is an instruction to trade.
Who it is for
Traders who already have levels in a note and are tired of watching the ladder by hand.
Job to be done
Fire a message when price tags a level you wrote, or when price enters a band around a liquidation cluster you marked as relevant.
Human gate. Every alert ends in your chat or inbox. You decide whether it still means what it meant when you wrote the level.
Inputs and outputs
Inputs
- A level file: market, price, side, reason, and what you intended to do if tagged
- The session window when alerts are allowed
- Optional: a liquidation estimate with source, time, and the band you care about
- A cap on alerts per market per hour
Outputs
- A message with market, print, level, reason you wrote, and time
- No order, no size suggestion
- A daily list of alerts you ignored, so dead levels get deleted
Step-by-step workflow
- 01Write the level fileMarket, price, why it exists, and the action you might take. If the action cell is empty, do not arm the alert.
- 02Arm a dumb triggerPrice cross or band entry. Keep the logic boring enough to debug when it misfires.
- 03Format the messageInclude the reason from the file, verbatim. Do not let a model rewrite your level into a new thesis.
- 04Cap and dedupeOne fire per cross, not one per tick. Silence the market outside the session window you set.
- 05Review ignored alertsOnce a day, list what fired and what you did. Delete dead levels in the same sitting.
- 06Human gateThe message is the product. Opening a ticket, a hedge, or nothing is your step, outside the agent.
Suggested tool types
These are categories of tools, not product picks. Crypto Agent Desk does not certify vendors and does not run an affiliate program.
| Type | Why it is here |
|---|---|
| Price or websocket feed | The trigger has to be a print, not a model guessing the tape. |
| Alert transport | Chat webhook, email, or push. Pick one you will actually see. |
| Liquidation or heat-map data source | Only if you already trust it. Label the figure as an estimate. |
| Chat model | Optional, to format the message. It should not invent levels. |
Risks and failure modes
Levels you did not write
If the agent suggests the level, you will not know why it fired. Only watch prices that are already in your file.
Cluster worship
Liquidation maps are estimates and they move. An alert that treats the map as a wall will spam you.
Alert fatigue
A level without a cap becomes a second chart. Delete any level you ignored twice.
Operator notes
The level file is the system. The alert is only a bell. If you would be embarrassed to read the “why” line out loud, the level is not ready.
Message shape
MARKET tagged PRICE at TIME. Your level: LEVEL. Your note: NOTE. This is not an order.
Prompt you can paste
Format alerts from this level file and this latest print. Do not add levels.
Level file: LEVEL_FILE
Print: PRINT with timestamp.
If the print has not crossed a level, say "no alert".
If it has, output: market, print, level, my note verbatim, time.
Do not suggest an order or a size. Mention the hourly cap CAP.Done when
A fired alert contains your own sentence, and you can delete a level without editing code in three places.
FAQ
Can the alert include a suggested order?
No. Put the intention you wrote when you were calm into the message. Do not compute a new order in the alert path.
How should liquidation data be labeled?
As an estimate from a named source, with a timestamp. If the source is missing, do not alert on it.
What is a good cap?
Low enough that a runaway feed cannot page you every minute. If you stop reading, the cap is still too high.
Published . Updated . This is an operating playbook, not a recommendation to buy, sell, or hold any asset.