Skip to main content

Notification

Notification settings (enable/disable, channels, recipients) can be configured directly from the Configuration page in the web UI.

This page covers additional setup guides for each channel.

Email​

Databasement uses Laravel's mail system (Symfony Mailer). Configure your mail driver with these environment variables:

Basic SMTP configuration (STARTTLS – typical 587)​

MAIL_MAILER=smtp
MAIL_HOST=smtp.example.com
MAIL_PORT=587
MAIL_SCHEME=smtp
MAIL_USERNAME=your-username
MAIL_PASSWORD=your-password
MAIL_FROM_ADDRESS=databasement@example.com
MAIL_FROM_NAME="Databasement"

smtp uses plain SMTP and automatically negotiates STARTTLS if the server supports it (commonly port 587).

SMTPS (implicit TLS – typical 465)​

MAIL_MAILER=smtp
MAIL_HOST=smtp.example.com
MAIL_PORT=465
MAIL_SCHEME=smtps
MAIL_USERNAME=your-username
MAIL_PASSWORD=your-password
MAIL_FROM_ADDRESS=databasement@example.com
MAIL_FROM_NAME="Databasement"

smtps enables implicit TLS from the beginning of the connection.

Unencrypted SMTP / no forced encryption (port 25)​

MAIL_MAILER=smtp
MAIL_HOST=smtp.example.com
MAIL_PORT=25
MAIL_SCHEME=smtp

If the server advertises STARTTLS, Symfony will attempt to use it automatically.

If you must explicitly disable STARTTLS, use a DSN:

MAIL_MAILER=smtp
MAIL_URL=smtp://smtp.example.com:25?auto_tls=false

Using a DSN (advanced configuration)​

You may configure the full connection using MAIL_URL:

MAIL_MAILER=smtp
MAIL_URL=smtp://user:pass@smtp.example.com:587

Or with implicit TLS:

MAIL_MAILER=smtp
MAIL_URL=smtps://user:pass@smtp.example.com:465

Note: If your username or password contains special URI characters (e.g. @, :, +, #), percent-encode them in the DSN (e.g. @ → %40).

When MAIL_URL is defined, it overrides MAIL_HOST, MAIL_PORT, MAIL_USERNAME, MAIL_PASSWORD, and MAIL_SCHEME.

Removed option​

MAIL_ENCRYPTION is no longer used.

Encryption behavior is controlled exclusively by the DSN scheme (smtp or smtps) and optional DSN parameters.

Slack​

To receive failure notifications in Slack, you need to create an Incoming Webhook:

  1. Go to Slack API Apps
  2. Click Create New App > From scratch
  3. Name your app (e.g., "Databasement") and select your workspace
  4. Go to Incoming Webhooks and toggle it on
  5. Click Add New Webhook to Workspace
  6. Select the channel where you want notifications
  7. Copy the webhook URL and paste it in the Configuration page

Discord Webhook​

The simplest way to receive failure notifications in Discord — no bot required.

  1. Open Server Settings > Integrations > Webhooks
  2. Click New Webhook
  3. Choose the channel where you want notifications
  4. Click Copy Webhook URL

Paste the Webhook URL on the Configuration page (select the Discord (Webhook) channel).

Tip: If you just need notifications in a single channel, Discord Webhook is easier to set up than the bot-based integration below.

Discord Bot​

To receive failure notifications in Discord via a bot, you need a bot token and a channel ID. This gives more flexibility (e.g., sending to multiple channels) but requires more setup.

Creating a Discord Bot​

  1. Go to Discord Developer Portal
  2. Click New Application and give it a name (e.g., "Databasement")
  3. Go to Bot in the sidebar and click Add Bot
  4. Under Token, click Copy to get your bot token
  5. Go to OAuth2 > URL Generator
  6. Select scopes: bot
  7. Select bot permissions: Send Messages, Embed Links
  8. Copy the generated URL and open it to invite the bot to your server

Getting a Channel ID​

  1. Open Discord and go to User Settings > Advanced
  2. Enable Developer Mode
  3. Right-click the channel where you want notifications
  4. Click Copy Channel ID

Enter both the Bot Token and Channel ID on the Configuration page (select the Discord (Bot) channel).

Telegram​

To receive failure notifications via Telegram, you need a bot token and a chat ID.

Creating a Telegram Bot​

  1. Open Telegram and search for @BotFather
  2. Send /newbot and follow the prompts to name your bot
  3. BotFather will give you a Bot Token — copy it

Getting a Chat ID​

  1. Add your bot to the group or start a direct chat with it
  2. Send a message to the bot
  3. Open https://api.telegram.org/bot<YOUR_BOT_TOKEN>/getUpdates in a browser
  4. Find the chat.id value in the JSON response

Enter both the Bot Token and Chat ID on the Configuration page.

Pushover​

Pushover delivers push notifications to your phone and desktop.

  1. Create an account at pushover.net
  2. Copy your User Key from the dashboard
  3. Go to Create an Application/API Token
  4. Name it (e.g., "Databasement") and copy the App Token

Enter both the App Token and User Key on the Configuration page.

Gotify​

Gotify is a self-hosted push notification server.

  1. Log in to your Gotify server
  2. Go to Apps and create a new application (e.g., "Databasement")
  3. Copy the App Token

Enter your Gotify Server URL (e.g., https://gotify.example.com) and the App Token on the Configuration page.

Webhook​

Send failure notifications as JSON payloads to any HTTP endpoint.

Enter your Webhook URL on the Configuration page. Optionally, provide a Webhook Secret to authenticate requests via the X-Webhook-Token header.

Request Format​

Notifications are sent as POST requests with a JSON body:

{
  "event": "BackupFailedNotification",
  "title": "Backup Failed: Production DB",
  "body": "A backup job has failed.",
  "fields": {
    "Server": "Production DB",
    "Database": "myapp"
  },
  "error": "Connection refused",
  "action_url": "https://your-instance.com/backup-jobs/...",
  "timestamp": "2025-01-15T02:00:00+00:00"
}

Headers​

HeaderDescription
Content-Typeapplication/json
X-Webhook-TokenThe configured secret (only if a secret is configured)

Tip: Using with Apprise​

The webhook channel can be pointed at an Apprise API endpoint to relay notifications to 100+ services (Ntfy, Matrix, Mattermost, etc.). Set the Apprise stateless endpoint (e.g., https://apprise.example.com/notify/) as your Webhook URL.

What Gets Notified​

Notifications are sent only for failures:

  • Backup failures: When a scheduled or manual backup fails
  • Restore failures: When a restore operation fails
  • Missing snapshots: When snapshot file verification detects missing backup files on storage volumes

Successful operations do not trigger notifications.

Notification Content​

Each notification includes:

  • Server name
  • Database name
  • Error message
  • Timestamp
  • Direct link to the failed job details