You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You just found one of the coolest tools on the Internet for a homelab enthusiast. We do notifications. We do them right. We've been doing then for years and we'll keep doing them for years to come. Notifiarr provides native custom integrations with dozens, maybe hundreds of applications and websites. That means these applications or websites can send data to Notifiarr, and we'll format a message according to your configuration then send it to your chat server.
28
+
You just found one of the coolest tools on the Internet for a homelab enthusiast.
29
+
We do notifications. We do them right. We've been doing then for years and we'll keep doing them for years to come.
30
+
Notifiarr provides native custom integrations with dozens, maybe hundreds of applications and websites.
31
+
That means these applications or websites can send data to Notifiarr, and we'll format a message according to
32
+
your configuration then send it to your chat server.
26
33
27
34
What sets us apart from direct integrations are the options we provide to format your messages. We also maintain and provide, for your conveince, a local agent you may run on any server or network you wish to monitor. The agent is fully configurable to collect network and system data so you can get health reports from your servers.
28
35
@@ -37,28 +44,33 @@ we have a big community, if you need assistance you can ask there by opening a s
37
44
38
45
## From the author
39
46
40
-
I built Notifiarr in late 2019 for [myself](https://github.com/austinwbest), and it was used by only myself until August of 2020 when I opened it up for others to use. My goal has always been to have a single location for common notification needs, so I am not jumping around 20 apps to do things. [Captain](https://github.com/davidnewhall) joined the crew in December 2020, and the two of us run the servers and write the code for the client and website.
47
+
I built Notifiarr in late 2019 for [myself](https://github.com/austinwbest), and it was used by only myself until
48
+
August of 2020 when I opened it up for others to use. My goal has always been to have a single location for common
49
+
notification needs, so I am not jumping around 20 apps to do things. [Captain](https://github.com/davidnewhall)
50
+
joined the crew in December 2020, and the two of us run the servers and write the code for the client and website.
41
51
42
52
## Integrations
43
53
44
54
!!! note
45
-
46
55
[How to setup integrations](pages/integrations/basicUsage.md#how-to-setup-integrations)
47
56
48
57
## Additional Features
49
58
50
-
* Fully configurable on what triggers to get notifications for. Each integration and many triggers in them can go to their own channels.
51
-
* Layout configuration for some notifications
52
-
* Content configuration for most notifications (color, content, etc)
53
-
* Media Requests Bot - Discord Bot for all 4 \*Arr apps with:
54
-
* Media Requests
55
-
* User Permissions
56
-
* Approvals
57
-
* Sonarr Profiles
58
-
* Default Options
59
-
* Series Following
60
-
* Discover features
61
-
* Multi-Instance Support
62
-
* Minimal Access - No \*Arr apikeys or anything of the sort is used or saved on the site. All requests to the client are verified with your Notifiarr apikey and thrown out if they don't match up
63
-
* TRaSH Custom Format Sync [*\*Patron Feature\**](pages/faq/faq.md#q-what-are-the-user-level-differences) - Automated continuous add/sync for the custom formats TRaSH has made to use with Radarr
64
-
* Radarr Collections - A fully automated way to monitor all your Radarr collections with auto add new items to your library as they are put into the collection on TMDb for any monitored collections, etc.
59
+
- Fully configurable on what triggers to get notifications for. Each integration and many triggers in them can go to their own channels.
60
+
- Layout configuration for some notifications
61
+
- Content configuration for most notifications (color, content, etc)
62
+
- Media Requests Bot - Discord Bot for all 4 \*Arr apps with:
63
+
- Media Requests
64
+
- User Permissions
65
+
- Approvals
66
+
- Sonarr Profiles
67
+
- Default Options
68
+
- Series Following
69
+
- Discover features
70
+
- Multi-Instance Support
71
+
- Minimal Access - No \*Arr apikeys or anything of the sort is used or saved on the site.
72
+
All requests to the client are verified with your Notifiarr apikey and thrown out if they don't match up
73
+
- TRaSH Custom Format Sync [*\*Patron Feature\**](pages/faq/faq.md#q-what-are-the-user-level-differences) -
74
+
Automated continuous add/sync for the custom formats TRaSH has made to use with Radarr
75
+
- Radarr Collections - A fully automated way to monitor all your Radarr collections with auto add new
76
+
items to your library as they are put into the collection on TMDb for any monitored collections, etc.
Copy file name to clipboardExpand all lines: docs/pages/client/configuration.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ When a new docker image is deployed with an empty /config folder mounted, the ap
21
21
- You can use env variables, the conf file, or the UI
22
22
- Must provide the "All" API key from your [Profile page on notifiarr.com](https://notifiarr.com/user.php?page=profile)
23
23
-**The Notifiarr application uses the API key for bi-directional authorization between the Site and the Client.**
24
-
24
+
25
25
!!! danger "Unraid Users"
26
26
You must configure the Notifiarr API Key in the Unraid Template/ Container Settings. If you wish to use Plex then you'll also need to set the Plex Token and Plex URL in the template as well. The other integrations can be defined in notifiarr.conf
27
27
@@ -131,7 +131,7 @@ Recommend not messing with these unless instructed to do so.
131
131
| max_body |`DN_MAX_BODY`| Unlimited, `0` / Maximum debug-log body size (integer) for payloads to and from notifiarr.com |
132
132
||`TMPDIR`|`%TMP%` on Windows. Varies depending on system; must be writable if using Backup Corruption Check |
133
133
134
-
_Note: You may disable the GUI (menu item) on Windows by setting the env variable `USEGUI` to `false`._
134
+
*Note: You may disable the GUI (menu item) on Windows by setting the env variable `USEGUI` to `false`.*
Copy file name to clipboardExpand all lines: docs/pages/client/gui.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ notifiarr.exe --reset
61
61
docker exec Notifiarr /notifiarr --reset
62
62
docker kill --signal=HUP Notifiarr
63
63
```
64
-
64
+
65
65
```bash
66
66
# Example output with new password:
67
67
[INFO] 2023/09/08 09:32:11 New 'admin' user password: four38=Draw
@@ -135,7 +135,12 @@ The General section is more catered to the ingress and egress options/functional
135
135
!!! warning
136
136
This API must be an All key!
137
137
138
-
1.`Extra Keys` - This application uses the Notifiarr.com API key (set above) for incoming authentication. It's not safe to give that key to any other website, person, or third party service. This is because that key is also used for authentication to the Notifiarr.com API. If you want third parties to authenticate to this application's API, you should create custom keys for each integration. As of March 8, 2022, there are no existing integrations, so this is for future use. You can use this section to add extra API keys. Whatever you want. Separate them with newlines or spaces.
138
+
1.`Extra Keys` - This application uses the Notifiarr.com API key (set above) for incoming authentication.
139
+
It's not safe to give that key to any other website, person, or third party service.
140
+
This is because that key is also used for authentication to the Notifiarr.com API.
141
+
If you want third parties to authenticate to this application's API, you should create custom keys for each integration.
142
+
As of March 8, 2022, there are no existing integrations, so this is for future use. You can use this section to add
143
+
extra API keys. Whatever you want. Separate them with newlines or spaces.
139
144
1.`Bind Address` - This is the IP and port the app will listen on. 0.0.0.0 means all IPs, and you should use that in almost all cases! Change the port if the default 5454 does not work for you.
140
145
1.`URL Base` - This application serves HTTP on / by default. You can change that by typing in something else here.
141
146
1.`Upstreams` - If Notifiarr client is behind a reverse proxy (swag, nginx, etc), then you should add that proxy IP here. You can also specify full networks. This controls which IP is written to the web server log file (requestor or x-forwarded-for header). It also allows the x-webauth-user header for proxy authentication. Separate with spaces or new lines.
Copy file name to clipboardExpand all lines: docs/pages/client/setup.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ There are non-integration related settings and triggers are configured on the No
21
21
1. Open the conf file, set your Notifiarr API Key and restart the client.
22
22
23
23
```conf
24
-
## This API key must be copied
24
+
## This API key must be copied
25
25
from your notifiarr.com account.
26
26
api_key = "api-key-from-notifiarr.com"
27
27
```
@@ -47,7 +47,7 @@ When a new docker image is deployed and an empty /config folder is mounted the a
47
47
- Must provide the "All" API key from your [Profile page on notifiarr.com](https://notifiarr.com/user.php?page=profile)
48
48
- **The Notifiarr application uses the API key for bi-directional authorization between the Site and the Client.**
49
49
50
-
!!! warning
50
+
!!! warning
51
51
**Unraid Users**
52
52
You must configure the Notifiarr API Key in the Unraid Template/ Container Settings. If you wish to use Plex then you'll also need to set the Plex Token and Plex URL in the template as well. The other integrations can be defined in notifiarr.conf
Copy file name to clipboardExpand all lines: docs/pages/discordbot/permissions.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,14 @@
1
1
# Discord Permissions
2
2
3
-
Getting permissions correct for your setup can be a struggle depending on how you have your Discord server setup. If you want to run a simple test to see if you have permission issues, set the Notifiarr role to have `Admin` permission and see whether it solves your issue. If everything works, this means you simply need to adjust permissions for the the Notifiarr role and you don't need to give it full admin permissions
3
+
Getting permissions correct for your setup can be a struggle depending on how you have your Discord server setup.
4
+
If you want to run a simple test to see if you have permission issues, set the Notifiarr role to have `Admin`
5
+
permission and see whether it solves your issue. If everything works, this means you simply need to adjust permissions
6
+
for the the Notifiarr role and you don't need to give it full admin permissions.
4
7
5
8
---
6
9
7
-
To update the integration's permissions, click on your server name at the top and pick `Server Settings > Roles`. Click on the `Notifiarr` role and then pick `Permissions`.
10
+
To update the integration's permissions, click on your server name at the top and pick `Server Settings > Roles`.
11
+
Click on the `Notifiarr` role and then pick `Permissions`.
Copy file name to clipboardExpand all lines: docs/pages/faq/faq.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,10 @@ If session info is missing from notifications or the sessions notification is no
89
89
- Make sure you have selected the **Activity** checkbox in the Plex section of the [Client Settings](../../pages/website/clientConfig.md)
90
90
- Try to increase the **Activity Delay** in the Plex section of the [Client Settings](https://notifiarr.wiki/en/Website/ClientConfiguration) as this will give Plex more time to get the session available in the endpoint
91
91
- Note 1: The sessions notifications will only send when there is at least one item being played or paused
92
-
- Note 2: It doesn't matter what Tautulli shows or the Plex Dashboard shows, they both use the same sessions endpoint. If you where to look at them at the same time as the notification is sent (when it doesn't work) they would also not show the session yet. How long it takes Plex & your (possibly low powered or over worked) server to make the session available in the endpoint is out of our control which is why we added the delay option
92
+
- Note 2: It doesn't matter what Tautulli shows or the Plex Dashboard shows, they both use the same sessions endpoint.
93
+
If you where to look at them at the same time as the notification is sent (when it doesn't work) they would also not
94
+
show the session yet. How long it takes Plex & your (possibly low powered or over worked) server to make the session
95
+
available in the endpoint is out of our control which is why we added the delay option
0 commit comments