Material events happen whether you are watching a dashboard or not. A 8-K filed at 4:30 p.m., a price gap at the open, or a press release during lunch. The desk that learns first acts first. Alerts exist so coverage does not depend on someone refreshing a browser tab at the right moment.
Vantafin does not offer Slack integration or webhook delivery. What we provide is email alerts in alerts for three event types: price alerts, filing alerts, and news alerts. This tutorial configures each type for a coverage universe drawn from your watchlists.
Configure price alerts
Open alerts and create a price alert for a ticker in your watchlists. Set the threshold (absolute price, percent change from prior close, or another condition the UI supports) and confirm email delivery. Price alerts fire when the condition is met during market hours, so you catch gaps and intraday moves without polling GET /quotes/{ticker} in a loop.
Test with a liquid name like Microsoft at a threshold you expect to trigger soon, or set a wide band for a pure delivery test. Confirm the email arrives with the ticker, condition, and timestamp in the right timezone before you replicate the rule across your universe.
Price alerts complement bulk quote dashboards. The dashboard gives continuous context for names you are watching; alerts catch moves on the long tail you are not staring at.
Configure filing and news alerts
Filing alerts notify you when covered tickers submit new SEC documents: 10-K, 10-Q, 8-K, Form 144, and other forms in our filing taxonomy. News alerts fire when press releases and headlines hit the wire for your symbols. Combine both with the F and N WebSocket channels when you want real-time metadata in a dashboard plus email as a backup channel.
Tune filing alerts by focusing on your watchlists rather than the entire market. For material 8-K monitoring, pair email alerts with search_filings via the MCP server for keyword triage after the email arrives. The email is the doorbell; the filing viewer and semantic search are the library.
Avoid alert fatigue by separating high-priority tickers into dedicated rules with tighter conditions, and batching lower-priority names into a single daily review habit rather than per-filing email for every 10-Q in a large universe.
Operate reliably
Review alert rules quarterly when your coverage universe changes. Stale watchlists are the most common failure mode: the alert system works, but the ticker list is six months old. Sync rules with watchlists you actually maintain.
Pair filing alerts with earnings dates on the calendar so you expect higher filing and news volume during earnings week. Plan limits: pricing. An alert that fires in seconds only helps if someone owns the read-through. Assign coverage in your team's runbook even though delivery is email, not Slack.
Email alerts that desks actually read
Material filings buried in a generic inbox often get read hours too late. Vantafin's alerts support three delivery types: price, filing, and news. Each is routed to email with filters that match how equity teams actually work. A filing alert should answer ticker, form type, time filed, and where to read in one glance on mobile between meetings.
Create filing alerts by form type) 10-K, 10-Q, 8-K (and bind the universe to watchlists or a screener export you refresh when coverage changes. Stale universes are the most common failure mode: the alert rule works, but the ticker list is six months old. Add keyword-oriented review through in-app filing search and search_filings in the MCP server when you narrow material 8-K monitoring to specific risk language.
Test with a liquid name like Microsoft to verify formatting before going wide. Confirm notifications arrive in the mailbox traders actually monitor, and document alert ownership in your internal runbook so coverage handoffs do not leave rules pointing at departed analysts.
Price and news alerts on the same stack
Filing alerts alone miss how the market responds. Pair them with price alerts on crosses above or below levels or percent change thresholds, plus news alerts filtered by publisher or general news rules on the same watchlist. During earnings season, a headline alert on N.{ticker} sometimes arrives minutes before the formal 8-K metadata hits F.{ticker} on the WebSocket; email rules on both layers keep you aligned without watching three screens.
On delivery, append context from bulk quote snapshots in your internal templates so readers see immediate market marks when they open the message. Material news with muted price response may mean the market already knew; showing the mark inline speeds that judgment.
Route high-priority filing forms to dedicated alert names such as "Critical 8-K" versus "Quarterly 10-Q" so traders learn which subjects demand immediate read-through. Severity routing is how you keep email trustworthy: if everything pings loudly, nothing is urgent.
Operating reliably at scale
Review false positives monthly. Keywords like "breach" catch cybersecurity incidents and also catch "no breach occurred" boilerplate in legal disclaimers. Tighten rules with negative filters when you see patterns, and dedupe by accession number if you run parallel monitors that might overlap the same filing.
Pair filing email with live F and N WebSocket subscriptions on catalyst names when you need sub-minute awareness beyond what email latency provides. Most desks use email for reliable delivery and the socket for continuous context on a short list. Confirm entitlements on pricing for alert frequency and symbol coverage before pointing production universes at hundreds of tickers.
Connect summarized follow-ups through the MCP server for three-bullet human-reviewed memos on the highest-priority alerts. Pair filing traffic with pre-earnings news drift scores during earnings season so readers know whether price already moved into the event.