The files have to define [nested templates](https://pkg.go.dev/text/template#hdr-Nested_template_definitions) in order to override the original values. An example:
{% raw %}
```
{{ define "title_success" -}}
✅ Successfully ran backup {{ .Config.BackupStopContainerLabel }}
-`title_success` (the title used for a successful execution)
-`body_success` (the body used for a successful execution)
-`title_failure` (the title used for a failed execution)
-`body_failure` (the body used for a failed execution)
## Notification templates reference
Configuration, data about the backup run and helper functions will be passed to these templates, this page documents them fully.
### Data
Here is a list of all data passed to the template:
*`Config`: this object holds the configuration that has been passed to the script. The field names are the name of the recognized environment variables converted in PascalCase. (e.g. `BACKUP_STOP_CONTAINER_LABEL` becomes `BackupStopContainerLabel`)
*`Error`: the error that made the backup fail. Only available in the `title_failure` and `body_failure` templates
*`Stats`: objects that holds stats regarding script execution. In case of an unsuccessful run, some information may not be available.
*`StartTime`: time when the script started execution
*`EndTime`: time when the backup has completed successfully (after pruning)
*`TookTime`: amount of time it took for the backup to run. (equal to `EndTime - StartTime`)
*`LockedTime`: amount of time it took for the backup to acquire the exclusive lock
*`LogOutput`: full log of the application
*`Containers`: object containing stats about the docker containers
*`All`: total number of containers
*`ToStop`: number of containers matched by the stop rule
*`Stopped`: number of containers successfully stopped
*`StopErrors`: number of containers that were unable to be stopped (equal to `ToStop - Stopped`)