Multi-channel alerts

Never miss a
critical event

Telegram, Discord, and email alerts for drops, bans, machine outages, and more. Configure exactly what you want to know about — and ignore the rest.

Overview

Stay informed without staying glued to the dashboard

Running a farming operation means things happen around the clock — drops are claimed, accounts get banned, machines go offline, jobs fail. You can't watch the dashboard 24/7, but you need to know when something important happens. That's what notifications are for.

Your channels, your rules

Vedor Labs lets you connect Telegram bots, Discord webhooks, and email addresses as notification channels. Each channel can be configured independently — send drop summaries to a Discord channel your team monitors, ban alerts to your personal Telegram, and daily reports to your email. You decide what goes where.

Smart, not noisy

Nobody wants to be bombarded with thousands of individual messages. Vedor Labs batches related events into summary notifications, throttles high-frequency alerts, and lets you set quiet hours. You get the information you need without the noise.

Features

Powerful alerts, zero noise

💬

Telegram Alerts

Connect your Telegram bot for instant mobile notifications. Rich formatting with account details, event type, and timestamps.

🎮

Discord Webhooks

Send formatted embed messages to any Discord channel. Perfect for team monitoring and shared awareness of your operation's status.

📧

Email Notifications

Receive daily digest emails or instant alerts for critical events. Clean formatting that works on any email client.

🎛️

Per-Event Configuration

Enable or disable notifications for each event type independently. Drops, bans, machine status, job failures — you choose what matters.

📦

Smart Batching

Bulk events are grouped into summary notifications instead of individual messages. 1,000 drops become one clean summary, not 1,000 pings.

🔕

Quiet Hours & Throttling

Set quiet hours to pause non-critical notifications. Built-in throttling prevents alert fatigue during high-activity periods.

Getting started

Set up alerts in under five minutes

01

Connect a channel

Add a Telegram bot token, Discord webhook URL, or email address in your notification settings. You can connect multiple channels of each type.

02

Choose your events

Select which event types you want to receive on each channel. Toggle drops, bans, machine alerts, job failures, and more — each independently.

03

Send a test notification

Hit the test button to verify your channel is connected and receiving messages correctly. Adjust formatting preferences if needed.

Ready to set up your alerts?

Connect Telegram, Discord, or email and start getting notified about what matters. Takes less than five minutes.

Get Started
FAQ

Notification questions

Common questions about alerts and notifications in Vedor Labs.

Vedor Labs supports Telegram, Discord (via webhooks), and email notifications. You can configure one or multiple channels and choose which event types go to which channel — for example, drop alerts to Telegram and ban notifications to email.
You can configure alerts for case drops, item drops, account bans (game bans, VAC bans, trade bans), machine outages, high resource usage, job failures, login errors, and trade completions. Each event type can be enabled or disabled independently per notification channel.
Yes. Just paste your Discord webhook URL in the notification settings. Vedor Labs sends formatted embed messages with relevant details — account name, event type, timestamp, and any associated data. Multiple team members can monitor the same webhook channel.
No. Vedor Labs includes intelligent throttling and batching. If 500 accounts receive drops in the same cycle, you get a single summary notification instead of 500 individual messages. You can also configure quiet hours and minimum severity levels to control notification volume.
Notifications are sent within seconds of the event occurring. Drop alerts fire as soon as the drop is detected and claimed. Machine offline alerts trigger after the configured heartbeat timeout (default 90 seconds). There is no polling delay — events are pushed in real time.
Explore more

More automation features