Wire alerts into your workflow
How to connect Telegram, Discord, email and webhooks so alerts land where you actually work.
Connect one channel first, watch it for a week, then add filters. Webhooks are the only channel that lets you act programmatically.
Alerts are only useful if they reach you where you already are. Delivery is configured per channel in your dashboard under Channels, and every alert we send is recorded under Deliveries so you can audit what arrived and when.
Telegram
The fastest channel to set up and the one most traders keep as their primary. Connect your account in Channels, then choose which chains and patterns you want. Alerts arrive with the score, cluster summary and a link back to the full card.
Discord
Point a channel webhook at your desk or community server. Useful when more than one person needs to see the same feed and discuss it in place.
Best used as a lower-frequency digest or as a backstop for high-score alerts only. Email adds seconds of latency you do not control, so do not make it your only channel if you trade the alert.
Webhooks
The only channel that lets you act programmatically. You receive the full signal payload — score components, cluster wallets, token risk, transaction hashes — as JSON, seconds after the block. Webhook delivery is an Elite-tier capability; the Developer section of your dashboard has the payload schema and a test endpoint.
Filters, and the mistake to avoid
Every channel supports filters by chain, pattern and minimum score. The common mistake is filtering hard on day one: you end up tuning against three alerts instead of thirty. Run one channel unfiltered for a week, see what you actually ignore, then filter that away.