If you're looking to trigger a custom script, you can find more details here. Scripts are added to Prowlarr via the Connect Settings.
Prowlarr can execute a custom script when an episode is newly imported or renamed. Depending on the action, different parameters are supplied. Parameters are passed to the script through environment variables.
Note that the following will only be logged for custom scripts:
stdout output will be logged as Debugstderr output will be logged as InfoTrace| Environment Variable | Details |
|---|---|
prowlarr_eventtype |
HealthIssue |
prowlarr_health_issue_level |
Type of health issue (Ok, Notice, Warning, or Error) |
prowlarr_health_issue_message |
Message from the health issue |
prowlarr_health_issue_type |
Source of the health issue |
prowlarr_health_issue_wiki |
Wiki URL for the health issue (Empty if it does not exist) |
| Environment Variable | Details |
|---|---|
prowlarr_eventtype |
HealthRestored |
prowlarr_health_restored_level |
Type of health issue (Ok, Notice, Warning, or Error) |
prowlarr_health_restored_message |
Message from the health issue |
prowlarr_health_restored_type |
Source of the health issue |
prowlarr_health_restored_wiki |
Wiki URL for the health issue (Empty if it does not exist) |
| Environment Variable | Details |
|---|---|
prowlarr_eventtype |
ApplicationUpdate |
prowlarr_update_message |
Message from the update |
prowlarr_update_newversion |
Version Prowlarr updated from (string) |
prowlarr_update_previousversion |
Version Prowlarr updated to (string) |
When adding the script to Prowlarr and clicking 'Test,' the script will be invoked with the following parameters. The script should be able to gracefully ignore any unsupported event type.
| Environment Variable | Details |
|---|---|
prowlarr_eventtype |
Test |