Set up notifications and Telegram alerts

Wevion notification setup overview. Verify current event types and delivery channels against backend defaults and Telegram routes.

Written By Salvatore Sinigaglia

Last updated About 4 hours ago

Wevion notification setup overview. Verify current event types and delivery channels against backend defaults and Telegram routes.

Set up notifications and Telegram alerts

Wevion supports in-app notifications, email delivery where enabled, push where configured, and Telegram integrations for selected alerts. Verify current event types and delivery behavior against apps/backend/src/lib/notification-defaults.ts and Telegram services before promising digest/quiet-hour behavior.

Who is this for

Everyone. The defaults are sensible but the Telegram bot is the single biggest quality-of-life upgrade for active media buyers.

The three channels

ChannelUse it forLatency
In-appBrowsing inside Wevion, low-urgency stuffReal-time when app open
EmailPer-event email where enabled; digest behavior must be verified before documentingvaries
TelegramReal-time alerts for rules, spend caps, errorsSeconds

You can mix and match per event type where the current preferences API exposes those toggles.

In-app notifications

Always on. The bell icon in the header shows unread count. Click it to open the panel — items grouped by type (Rules, Sync, Team, Billing).

Items disappear from the unread badge once you open the panel. They stay in the history for 30 days.

Email

Configure at Settings → Personal → Notifications (/settings/personal/notifications). The exact digest options available (cadence, sections) depend on your current version.

Email lands in the inbox of the email on your account when the event type/channel is enabled. To send to multiple addresses use email forwarding rules on your side.

Real-time alerts straight to your phone via Telegram. Setup takes 2 minutes.

Step 1: Open the connector page

In the sidebar click Connect → Telegram or jump to /connect/telegram. The page shows a one-time deep-link token and a button Open the Wevion Bot in Telegram.

Step 2: Open the bot

Click the Open the Wevion Bot in Telegram button. Telegram opens (or shows install prompt if not installed). You see a chat with the official Wevion bot.

Step 3: Send /start with your code

In the bot chat, send /start [your token] exactly as shown on the Wevion page. The bot replies with a welcome message confirming the connection.

Step 4: Configure what gets sent

Back in Wevion at /connect/telegram you now see a checklist of notification types. Toggle on:

  • Rule firings — every time an automation rule executes
  • Spend alerts — when daily spend exceeds a threshold
  • Sync errors — when a platform connection breaks
  • Token expiry — 7 days before any OAuth token expires
  • Digest — only if the current Telegram digest service is enabled for your workspace/user

Save. Within 30 seconds you should receive a test notification.

Step 5: Telegram bot commands

The bot also responds to commands in chat:

  • /status — short summary of all connected accounts
  • /spend today — today's spend per platform
  • /campaigns top — top 5 campaigns by spend in last 7 days
  • /pause [campaign-id] — pause a campaign (admin/manager/mediabuyer only)
  • /help — full command list

Multiple workspaces? Use /workspace [name] to switch the bot's active workspace.

Best-practice notification setup

A pattern that works for most:

  • In-app: everything, default
  • Email: enable only for events you want in your inbox; verify whether digest exists in the current UI
  • Telegram:
    • Rule firings: ON for pause and scale actions, OFF for notify-only rules (otherwise too noisy)
    • Spend alerts: ON, threshold = 120% of average daily spend
    • Sync errors: ON
    • Token expiry: ON

Adjust after 1 week based on noise levels.

What you'll see

After Telegram setup:

  • Connector card at /connect/telegram shows Connected in green
  • Your Telegram bot chat shows the bot active
  • A confirmation message: "Your Wevion alerts are connected"
  • First real notification arrives within minutes of the first matching event (rule firing, spend update, etc.)

Common issues

  • Auth code not accepted: code expires after 5 minutes. Refresh the connector page for a new one.
  • Bot doesn't reply to /start: the bot may be temporarily offline. Wait 1 minute and retry. Persistent: contact support.
  • Too many Telegram notifications: turn off notify-only rules where exposed; otherwise use Telegram's per-chat mute.
  • Wrong workspace alerts: send /workspace [name] in the bot chat to switch.
  • Email never arrives: check spam, whitelist noreply@wevion.ai, and verify the event type has email enabled in current preferences.

FAQ

What notification channels does Wevion support?

Wevion supports in-app notifications, email delivery where enabled, push where configured, and Telegram integrations for selected alerts. In-app is always on via the bell icon in the header, email is configured at Settings → Personal → Notifications, and Telegram delivers real-time alerts for rules, spend caps, and errors straight to your phone.

How do I connect the Wevion Telegram bot?

Open Connect → Telegram in the sidebar (or /connect/telegram), which shows a one-time deep-link token. Click Open the Wevion Bot in Telegram, then send /start [your token] in the bot chat exactly as shown. The bot replies confirming the connection, and within 30 seconds you should receive a test notification. Setup takes about 2 minutes.

What commands does the Wevion Telegram bot support?

The Wevion Telegram bot responds to /status for a summary of connected accounts, /spend today for spend per platform, /campaigns top for the top 5 campaigns by spend over the last 7 days, /pause [campaign-id] to pause a campaign, and /help for the full list. Use /workspace [name] to switch the active workspace.

Why isn't my Telegram connection code being accepted?

The deep-link token expires after 5 minutes for security. If the code isn't accepted, refresh the /connect/telegram page to generate a new one and send /start [new token] again. If the bot doesn't reply to /start at all, it may be temporarily offline — wait a minute and retry, then contact support if it persists.