Know when it matters — and nothing else

Email, Telegram, webhooks, local scripts, and in-app tray popups. Trigger on success, failure, or completion with errors. Configure once, enable per backup.

5 channels Per-backup triggers Configure once, reuse

A backup you never hear about is a backup you can't trust. BackupKit tells you when a run succeeds, fails, or finishes with some files behind — through whatever channel you already watch — and stays quiet the rest of the time. Set the channels up once, then flip any combination on or off per backup job.

Five ways to get notified

Email (SMTP)

Point BackupKit at any SMTP server — Gmail, your company mail, a transactional provider like Postmark. Templated subject and body per event type.

Telegram

Create a bot, paste the token and chat ID, done. Ping your phone or a private group when something needs attention.

Webhooks

POST a configurable JSON payload to any URL. Route into Slack, Discord, PagerDuty, n8n, Zapier, your own homelab dashboard — anywhere.

Local scripts & apps

Launch any executable or batch script on a backup event — sync to a second destination, fire a PowerShell command, kick a CI job. With configurable arguments.

In-app tray popup

A custom popup near your Windows tray — subtle, doesn't stack up, doesn't trip Focus Assist. Unlike Windows toasts, BackupKit owns the UI.

Your idea?

Missing a channel? Tell us — new integrations get prioritized by request count.

BackupKit webhook notification setup showing HTTP method and URL fields inside the backup's notification settings
Each channel expands into its own settings — a webhook just needs a method and a URL.

Trigger on the events that matter

Every integration can fire on any combination of three events. Telegram on failures but email on successes? Webhooks on everything? Silent unless something breaks? Mix however you want.

  • On success: run completed, files arrived. Usually silent unless you want the reassurance.
  • Completed with errors: the run finished, but some files didn't make it. A dropped connection partway through a large set is the usual cause — often the most useful signal, because nothing looks broken from the outside.
  • On failure: transfer error, auth issue, disk full. The one you almost always want on.
Notifications panel
Three events — success, completed with errors, and failure — can each be routed to any of five channels: email, Telegram, a webhook, a local script, or the tray popup. Every integration picks its own combination.
Any event, to any channel. Telegram on failures, email on successes, if you like.

Real setups people actually run

The quiet setup

Email on failure, silent otherwise. You only hear from BackupKit when something actually needs you.

The paranoid sysadmin

Telegram on failures and partial runs, webhook on success into a monitoring dashboard. Full audit trail.

The automation chain

A local script on success rsyncs the archive to a second physical disk — two-destination 3-2-1 backup with one click.

The team backup

Webhook into a shared Slack or Discord channel, so the whole team sees when the nightly client-data backup ran.

Back up anything, anywhere — today

Encrypted, scheduled, automated backups to storage you already own. Try every feature free for 30 days — no card required.

AES-256 encryption 30-day free trial Windows 10 & 11