Monitoring & Alerts
Automate real-time on-chain event detection and condition-based alerting to build responsive services. Instead of continuously polling blockchain nodes, use event-driven architecture to implement deposit detection, large transfer alerts, and custom event filtering without polling. From an institutional continuity perspective, the core requirement is to keep monitoring active even during disruptions.
What You Can Build
Automated Deposit Detection
As soon as assets arrive at a designated address, send a Webhook notification to an internal settlement system or ERP. This automates deposit confirmation and settlement processing without manually checking blockchain state.
Compliance Threshold Alerts
When asset movement exceeds a defined amount, automatically notify the compliance team. Use Webhook conditions to set thresholds based on transaction amount, specific addresses, or token type, and build a monitoring framework aligned with regulatory requirements.
Custodial Wallet Anomaly Detection
Receive alerts the moment abnormal asset movement occurs in custodial wallet addresses. Register separate Webhooks by wallet and connect them to anomaly detection workflows for faster response to wallet security events.
Real-Time Data Pipelines
Use Stream to receive block creation events and filtered on-chain data continuously over WebSocket. This is useful for delivering real-time on-chain data to internal analytics systems and risk engines.
Precision Condition-Based Alerts
With Flexible Webhook, define conditions in detail through CEL expressions and receive only the fields you need. This supports operational scenarios such as detecting large token movements, specific contract events, or only successful Transaction Receipts.
Key Capabilities
The following capabilities help you build on-chain monitoring and alerting systems.
Key Features
Automatically send HTTP POST requests to registered Callback URLs when defined on-chain events occur. This supports condition filters, retry/backoff policies, and Signing Key-based signature verification.
Receive block creation events and filtered on-chain data in real time through persistent WebSocket connections. This is well suited for analytics systems and risk engines that require continuous event delivery.
Use eth_subscribe to subscribe directly to low-level blockchain events. New blocks, pending transactions, and log events can be received through Elastic Node WebSocket Endpoints.
Use CEL conditions, selectable output fields, Live Sample, and Test Webhook to validate alert rules precisely before production rollout. This is also useful for failure handling through delivery history and Easy Resend.
Detect events before block finalization to support proactive risk detection and immediate user feedback. In finality-sensitive scenarios, combine it with standard Webhook or Stream.
Move beyond recording events to interpreting them in real time for dashboards, risk response, and internal notification systems. This turns deposit detection and anomaly monitoring into operational intelligence.
Webhook is a good fit when you only need to receive data when events occur. Stream is a better fit when you need persistent connections and continuous real-time delivery at the block or event level.
How It Works
Build on-chain monitoring through the following process:
- Create a Webhook or Stream subscription in the Nodit Console or through API
- Define the target event types to monitor, such as deposits, large asset movements, or contract events, and configure condition filters such as addresses, amounts, or token types
- If you need precise rule control, configure CEL expressions and output fields in Flexible Webhook, then validate them through Live Sample or Test Webhook
- Register the Callback URL for Webhook or the WebSocket Endpoint for Stream
- When an event occurs, Nodit automatically delivers it to the registered Endpoint
- Connect the delivery pipeline to internal systems such as settlement, compliance, or risk engines
API Endpoints
The table below maps common monitoring and alerting requirements to the corresponding Nodit features.
| Requirement | Feature | Product | Reference |
|---|---|---|---|
| Receive HTTP callbacks when events occur | Webhook | Webhook | Webhook |
| Build precision alerts with CEL conditions | Flexible Webhook | Webhook | Flexible Webhook Overview |
| Review Flexible Webhook stream types | Stream Type Catalog | Webhook | Flexible Webhook Stream Types |
| Review delivery history and execution status | Get Webhook History | Webhook | Get Webhook History |
| Stream on-chain data in real time | Stream | Stream | Stream |
| Review Stream event types | Stream Event Type | Stream | Stream Event Type |
| Subscribe to node-level WebSocket events | eth_subscribe | Elastic Node | API Reference |
Related Guides
- Webhook — Create Webhooks and configure event types and conditions
- Flexible Webhook Overview — Configure CEL conditions, output fields, and console-based operations
- Stream — Create Stream subscriptions and connect over WebSocket
- Elastic Node — Configure
eth_subscribeand WebSocket Endpoints - API Reference — Review full API parameters and response schemas
Create a free project in the Nodit Console and try Webhook and Stream directly.