Push Notifications

Get alerts when backups finish or fail.

Limitations

Notifications are sent only to the endpoint you configure.
If the endpoint is offline, messages may be lost.

macOS Notifications

Enable in FilmCan Settings
Configure style in System Settings > Notifications > FilmCan

ntfy (Phone/Remote)

Create a free account at https://ntfy.sh (or use a self‑hosted ntfy) and install the app on your phone.
Create a topic: e.g. ntfy.sh/mymovie_backup
Paste the topic URL in FilmCan Settings
(Optional) Paste a Bearer token if your topic requires auth

Webhook

Send a JSON payload to your own endpoint (Discord, Slack, custom server, etc.).

Enable Webhook in FilmCan Settings
Paste your Webhook URL
(Optional) Add Custom headers (one per line, Header: Value)

Payload format:

{
  "title": "...",
  "message": "...",
  "fields": {
    "movie": "...",
    "source": "...",
    "destination": "...",
    "sources": "...",
    "destinations": "...",
    "backupAction": "...",
    "bytes": "...",
    "files": "...",
    "duration": "...",
    "backupStatus": "...",
    "backupDetails": "..."
  }
}

The title and message use the same templates as ntfy. Use custom headers to add auth tokens (e.g., Authorization: Bearer <token>).

What You'll Get

Backup complete / failed (per destination)

Troubleshooting

No macOS alerts
System Settings > Notifications > FilmCan

ntfy not working
Check topic URL and internet connection

"FilmCan wants to access your confidential information" after an update
This is expected, and it is about your ntfy bearer token. The token is stored in your macOS keychain, and the keychain ties access to the exact copy of the app that saved it. A new version is a different copy, so macOS asks you to confirm once. Click Always Allow and the token works again until the next update. Your token is not lost.

If you clicked Deny, or if the dialog never appeared, FilmCan sees no token and the field in Settings looks empty: paste the token again and it will be saved normally.

Removing the prompt entirely would require signing FilmCan with a paid Apple certificate, which would publish the developer's legal name and email inside the app. That trade is deliberately not made.

Webhook not working
Check URL, SSL/TLS, and your endpoint logs

Transfer History