Scout notifications

Scout can post to an ntfy topic after a job uploads successfully in a scheduled cycle or Run Backup Cycle Now. Force Upload doesn’t notify from Scout, but Station still can. A failed notification never blocks an upload.

Station has separate notification settings that fire when it stores an upload. See Station notifications. Use either or both.

Set up

Open the dialog

In Scout, click Configure ntfy.

Enter your server and topic

ntfy Server URL: for example https://ntfy.sh or your own server.
Topic: for example backups.

Test and save

Click Test to send a sample message, then Save.

If your ntfy server uses a private CA, add it under Trusted certificates.

Message template

The default message is:

Scout uploaded {{ scout_id }}/{{ scout_instance_id }} job {{ job_name }} to Station as {{ stored_as }}.

Write your own in Message Template. Defaults restores the default.

Placeholder	Value
`{{ scout_id }}`	This Scout’s ID
`{{ scout_instance_id }}`	This Scout installation’s instance ID
`{{ job_name }}`	Name of the backup job
`{{ stored_as }}`	Filename as stored on Station

Messages are sent with the header X-Relay-Event: upload-finished.

Unusual backup alerts

When a backup looks very different from its history, Scout also sends a separate high-priority alert to the same topic, with the reasons. It uses the header X-Relay-Event: unusual-backup and ignores the message template. See Unusual backups.

​Set up

​Message template

​Unusual backup alerts

Set up

Message template

Unusual backup alerts