Hello Unraiders,

I recently had my server offline for a while (~5 months) due to some technical issues and updated from 7.0 -> 7.1.4 when I was able to get it back online. Since it was so long since I had the server on, I was giving it a bit of a configuration cleaning; going through all the options to make sure things are set up correctly after the gap in updates.

When I went in the Notifications Settings (Settings -> User Preferences -> Notification Settings), I noticed that the Join agent I am using was no longer listed as an option. Since I had this agent configured before it was removed somewhere along the line, I am still getting notifications via this agent with my previous settings intact and valid (/boot/config/plugins/dynamix/notifications/agents/Join.sh). I did a search on the Unraid forum and Unraid OS change logs to see when this feature was depreciated, but I could not find anything referencing Join.

Does anyone have any ideas on why this agent was removed? Was there something malicious I should be worried about?

I am open to switching notification services, but other than running my own Gotify server to ensure true security by not having another service in the middle, none of the options seem any more appealing than Join.

Edited October 12, 2025Oct 12 by JesterEE
typo

Please post a diag file...

Unless you added custom adational agent html config files. I don't recognize that notfication agent "JOIN" nor have I seen that agent on Unraid natively.

These are the current notification agents on unriad 7.1.4: https://github.com/unraid/webgui/tree/master/emhttp/plugins/dynamix/agents

What you may have may be a old agent from v5 or older or a depriacted plugin... Regardless this tell me that you have a custom html page that is rendering apart of the dynmax webui system.

I would first think that you have a docker running join-bot:

or an additional plugin like(simlar example):
https://forums.unraid.net/topic/168775-plugin-web-push-notification-agent/
https://github.com/Peuuuur-Noel/unraid-web-push-notification

that may be adding other agents.

I'm alos not finding the doc and other notification information so a agent change may have happened

Edited October 12, 2025Oct 12 by bmartino1

@Squid

Version 7.0.0 2025-01-09 | Unraid Docs

This version of Unraid OS includes significant improvements across all subsystems, while attempting to

how hard would it be to make a JOIN agent plugin again?

https://github.com/Squidly271/Wxwork-sample

Edited October 17, 2025Oct 17 by bmartino1

I too am missing the JOIN notification agent I had previously on 6.12. I upgraded to 7.2.

Then someone will need to share their old join xml so i can rebuild it...

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#notification-agents

https://docs.unraid.net/unraid-os/release-notes/6.12.15/#changes-vs-61214

as I can potentially see when and where the agents were reset and brought back to known working defaults.

The join agent is 3rd party and with email not setup it apparently borked and broke other agent handling in the unraid web ui.

so this join agent will need to become a 3rd paty plugin to restore and fix/rebuild its orginaly functionality...

Make a bug report and contact support...

Plugins are out of my wheelhouse...

that said we can potently pull the OG notification IF it exists via downloading the legacy version and garbing the necessary agent files:
https://docs.unraid.net/unraid-os/download_list/
*This would download a empty folder and populate by git clone... so whatever notification you had previously configured may be gone...

Edited November 2, 2025Nov 2 by bmartino1
spelling

as I don't know what this agent is doing nor how it interacted with unraid. I'm alos not 100% convinced that this agent existed in v6 (as I don't see it in my older unraid system using a tesla p4 with vgpu...)

https://joaoapps.com/join/desktop/

i could see a docker using a vnc web gui running to implement this...
https://github.com/joaomgcd/JoinDesktop/releases

as a docker image may exist or could be built to restore functionality...

It was located under the Settings --> Notifications like all the other modes. Where would I find the JOIN xml? Doing a quick search of my flash backup I did find this bash script, join.sh. Copy and pasted below as it's pretty basic. I've removed my API key.

#!/bin/bash
##########
API_KEY="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
TITLE="$SUBJECT"
MESSAGE="$DESCRIPTION"
##########
TITLE=$(echo -e "$TITLE")
MESSAGE=$(echo -e "$MESSAGE")
curl -s -k -G \
-d "apikey=$API_KEY" \
--data-urlencode "title=$TITLE" \
--data-urlencode "text=$MESSAGE" \
-d "deviceId=group.all" \
https://joinjoaomgcd.appspot.com/_ah/api/messaging/v1/sendPush 2>&1

Join.sh

Edited November 3, 2025Nov 3 by kimocal

Thank you, this is at least a start..

we would have to make that xml file and write some code to add this file into the notification.

This appears to be the end step script.... so the plugin (the xml file) will need areas to write the initial configuration data and to grab notification events that file... the title, message etc... and the data needed to connect to "join" as the agent... then this script is ran with that data filled in or generated....

Then this script (posted above appears to run) and is run to send the notification filling in the data to the join api system...

I'd have to go back and I have recently cleaned up old data... so it may be part of the old .page file in the emhttp example:
https://github.com/unraid/webgui/blob/master/emhttp/plugins/dynamix/NotificationAgents.page

SO, its hard to say, as I went searching old new etc... even on the unraid flash using grep and can't find any previous history edits of this existing natively. I'm not saying it didn't exist! Clearly something did... I'm just saying that its inital code can no longer be found... so it needs recreated...

Docker on CA and plugin on CA required different things in different github setups. and I'm not a fan of unraids emhttp we server and how it does what it does... as posted already as squid gave use a template we could build....

example:
https://github.com/Squidly271/Wxwork-sample

we will need to esential rebuild this join agent so a plugin thatwould sit in
/boot/config/plugins/ where the join.sh and other xml conifg page...

so the ca plugin template xml page to install from ca...

the setting page xml/http code to add the api key, the xyz data that is sent to this join.sh script and ran...

so My 2 blocks currently are:
I'm just not sure how nor what the notify system did to grab to then send to the agent to make its message...

I'm not going to be able to m,ake a plugin to share once configured.. I'm more then happy to work thoguh iissuesand help script a way around this.

as example here:
https://forums.unraid.net/topic/194631-plugin-or-script-that-can-function-as-a-docker-watchdog/#findComment-1587981

I'm not sure where nor how to tap unraid notfication to generate the message to the join api...

where I could edit the docker name set the words "unifi" on the message to container name var at the top and make notifications.

where this agent would somehow intercept and take that message and send it to xyz message over join...

So its a bit over my head as I don't know what this agen did nor how to workaround fix.

posblie to make a github issues linking this post and asking the unraid dev to look at the old code and see what they can scrape together.

"join" is to generic of a word and its hard geting and finding this data...

https://github.com/unraid/webgui/issues

as i'm not sure how i wouold code the 3rd party plugin to interact and use teh unraid web ui settings..


I left smtp email due to 2fa and app password BS (had google, microsft email smtp for a time...)... I dabbled in agents like slacc, discord messaging and found it easier and better to script and code that into my checks I wanted then trying to mess with unriads notification system...

All I can say is this would need recreated and implemented, and I don't have the data, access and ability to do at this time. Everything post so far helps tremendous but this will take time.

unraid doesn't really have clear documentation on how to code for its plugins...

using AI atempts to recreate files...

let’s bring the old Join notification agent back into Unraid’s Notifications UI.

Below are three drop-in artifacts:

1. a proper Agent XML (Join.xml) so it shows up under Settings → Notifications → Agents,

2. a minimal plugin installer (join-agent.plg) that persists the XML on the flash drive and copies it into RAM on boot,

3. an optional standalone shell (/boot/config/plugins/dynamix/notifications/agents/Join.sh) you can keep using for quick tests or fallbacks.
   

I matched the style of Dynamix’ built-in agents (e.g., Discord) and Squid’s sample agent. The XML uses the {0} injection point so values you set in the UI land at the top of the script automatically.
https://github.com/unraid/webgui/blob/master/emhttp/plugins/dynamix/agents/Discord.xml

GitHub

GitHub - Squidly271/Wxwork-sample

Contribute to Squidly271/Wxwork-sample development by creating an account on GitHub.

1) Join.xml (agent definition)

Save this as:
/boot/config/plugins/dynamix/agents/Join.xml (persistent)
The plugin below will copy it to RAM at:
/usr/local/emhttp/plugins/dynamix/agents/Join.xml

<?xml version="1.0" encoding="utf-8"?>
<Agent>
  <Name>Join</Name>

  <Variables>
    <Variable Help="Your Join API Key from https://joaoapps.com/join/" Desc="API Key" Default="">API_KEY</Variable>
    <Variable Help="Device or group target. Use 'group.all' to broadcast to all your Join devices, or a specific deviceId." Desc="Device Id" Default="group.all">DEVICE_ID</Variable>
    <Variable Help="Fields included in the notification title. Defaults to the Unraid SUBJECT." Desc="Notification Title" Default="$SUBJECT">TITLE</Variable>
    <Variable Help="Fields included in the message body. Defaults to Unraid DESCRIPTION + CONTENT + LINK when present." Desc="Notification Message" Default="$DESCRIPTION\n\n$CONTENT\n$LINK">MESSAGE</Variable>
  </Variables>

  <Script>
    <![CDATA[
#!/bin/bash
############
{0}
############

# Join Notification Agent for Unraid
# Based on the Dynamix agent format (see Discord.xml).
#
# Files & logs:
#   Script path (RAM): /boot/config/plugins/dynamix/notifications/agents/Join.sh
#   Log file:          /var/log/notify_Join
#
# Quick tests:
#   1) Dry run with env vars (bypasses notify):
#      EVENT="My Event" SUBJECT="My Subject" DESCRIPTION="My Description" CONTENT="Body text" IMPORTANCE="alert" LINK="/Dashboard" bash /boot/config/plugins/dynamix/notifications/agents/Join.sh
#
#   2) Full Unraid notify path:
#      /usr/local/emhttp/webGui/scripts/notify -e "My Event" -s "My Subject" -d "My Description" -m "My Message" -i "alert" -l "/Dashboard"
#
# If a notification doesn't go through, check /var/log/notify_Join

SCRIPTNAME=$(basename "$0")
LOG="/var/log/notify_${SCRIPTNAME%.*}"

# ---- Pull fields the same way as other agents (Discord) ----
EVENT="${EVENT:-Unraid Status}"
SUBJECT="${SUBJECT:-Notification}"
DESCRIPTION="${DESCRIPTION:-No description}"
IMPORTANCE="${IMPORTANCE:-normal}"
CONTENT="${CONTENT:-}"
LINK="${LINK:-}"
HOSTNAME="${HOSTNAME:-$(hostname)}"
TIMESTAMP="${TIMESTAMP:-$(date +%s)}"

# If LINK is a relative path, expand to GUI base URL
if [[ -n "${LINK}" ]] && [[ ${LINK} != http* ]]; then
  if [[ -r /usr/local/emhttp/state/nginx.ini ]]; then
    # shellcheck disable=SC1090
    source <(grep "NGINX_DEFAULTURL" /usr/local/emhttp/state/nginx.ini || true)
    LINK="${NGINX_DEFAULTURL}${LINK}"
  fi
fi

# Discord has a bare-hostname guard; Join doesn't care, but we'll keep LINK only if it looks usable.
if [[ -n "${LINK}" ]]; then
  HOST="$(echo "${LINK}" | cut -d'/' -f3)"
  [[ -z "${HOST}" ]] && LINK=""
fi

# ---- Build final TITLE / MESSAGE respecting agent-level overrides ----
# The UI Variables come in as literals that may include $SUBJECT, $DESCRIPTION, etc.
# Evaluate them after we’ve populated the notify variables so the defaults expand.
_expander() {
  # Expand \n, etc, then allow variable expansion (SUBJECT, DESCRIPTION, CONTENT, LINK...)
  # shellcheck disable=SC2016
  local raw="$1"
  # First interpret escapes
  local with_escapes; with_escapes="$(echo -e "$raw")"
  # Then expand env vars safely
  eval "echo \"$with_escapes\""
}

FINAL_TITLE="$(_expander "${TITLE:-$SUBJECT}")"
# Default MESSAGE concatenates description/content/link but strips the "No description" placeholder.
[[ "${DESCRIPTION}" == "No description" ]] && DESCRIPTION=""
DEFAULT_BODY="$(printf "%s\n\n%s\n%s" "$DESCRIPTION" "$CONTENT" "$LINK")"
FINAL_MESSAGE="$(_expander "${MESSAGE:-$DEFAULT_BODY}")"

# ---- Add a small importance prefix (emoji text). You can tweak this mapping. ----
case "${IMPORTANCE}" in
  alert)   IMP_PREFIX="(ALERT) ";;
  warning) IMP_PREFIX="(WARN)  ";;
  *)       IMP_PREFIX="";;
esac
FINAL_TITLE="${IMP_PREFIX}${FINAL_TITLE}"

# ---- Validate required settings ----
if [[ -z "${API_KEY}" ]]; then
  echo "Missing Join API key; set it in Settings → Notifications → Agents → Join." >>"$LOG"
  logger -t "$SCRIPTNAME" -- "Join: Missing API key"
  exit 1
fi

DEVICE="${DEVICE_ID:-group.all}"

# ---- Call Join REST API ----
# Docs: https://joaoapps.com/join/api/
# Endpoint (classic): https://joinjoaomgcd.appspot.com/_ah/api/messaging/v1/sendPush
# We use GET with urlencoding for title/text/deviceId/apikey, as in prior working scripts.

JOIN_URL="https://joinjoaomgcd.appspot.com/_ah/api/messaging/v1/sendPush"

# Convert newlines to \n for transport while keeping them readable on device
# Join will happily accept real newlines as well, but urlencode handles them either way.
TITLE_ENC=$(echo -ne "$FINAL_TITLE")
BODY_ENC=$(echo -ne "$FINAL_MESSAGE")

# Try a couple times in case of transient issues
MAX=3
for ((i=1; i<=MAX; i++)); do
  ret=$(curl -s -k -G \
    --data-urlencode "title=${TITLE_ENC}" \
    --data-urlencode "text=${BODY_ENC}" \
    -d "deviceId=${DEVICE}" \
    -d "apikey=${API_KEY}" \
    "${JOIN_URL}" 2>&1)

  # Join returns JSON; success contains "success": true
  if echo "$ret" | grep -q '"success": *true'; then
    exit 0
  fi

  {
    date
    echo "attempt $i of $MAX failed"
    echo "$ret"
  } >>"$LOG"

  (( i < MAX )) && sleep 1
done

logger -t "$SCRIPTNAME" -- "Join: Failed sending notification"
exit 1
    ]]>
  </Script>
</Agent>

---

2) join-agent.plg (tiny plugin to persist the agent)

Save this as: /boot/config/plugins/join-agent.plg and install via Plugins → Install Plugin → ‘Install from disk’ (or installplg /boot/config/plugins/join-agent.plg from SSH).

This keeps a copy of the agent on your flash and copies it to RAM on boot—same pattern as Squid’s sample.

<?xml version="1.0"?>
<PLUGIN name="join-agent" author="you" version="2025.11.04" pluginURL="" supportURL="https://forums.unraid.net/" min="6.10.0">
  <CHANGES>
    2025.11.04 - Initial release: Join notification agent for Unraid.
  </CHANGES>

  <!-- Persist the agent XML on the flash (source of truth) -->
  <FILE Name="/boot/config/plugins/dynamix/agents/Join.xml">
<![CDATA[
<?xml version="1.0" encoding="utf-8"?>
<Agent>
  <Name>Join</Name>
  <Variables>
    <Variable Help="Your Join API Key from https://joaoapps.com/join/" Desc="API Key" Default="">API_KEY</Variable>
    <Variable Help="Device or group target. Use 'group.all' to broadcast to all your Join devices, or a specific deviceId." Desc="Device Id" Default="group.all">DEVICE_ID</Variable>
    <Variable Help="Fields included in the notification title. Defaults to the Unraid SUBJECT." Desc="Notification Title" Default="$SUBJECT">TITLE</Variable>
    <Variable Help="Fields included in the message body. Defaults to Unraid DESCRIPTION + CONTENT + LINK when present." Desc="Notification Message" Default="$DESCRIPTION\n\n$CONTENT\n$LINK">MESSAGE</Variable>
  </Variables>
  <Script>
    <![CDATA[
#!/bin/bash
############
{0}
############
SCRIPTNAME=$(basename "$0")
LOG="/var/log/notify_${SCRIPTNAME%.*}"
EVENT="${EVENT:-Unraid Status}"
SUBJECT="${SUBJECT:-Notification}"
DESCRIPTION="${DESCRIPTION:-No description}"
IMPORTANCE="${IMPORTANCE:-normal}"
CONTENT="${CONTENT:-}"
LINK="${LINK:-}"
HOSTNAME="${HOSTNAME:-$(hostname)}"
TIMESTAMP="${TIMESTAMP:-$(date +%s)}"
if [[ -n "${LINK}" ]] && [[ ${LINK} != http* ]]; then
  if [[ -r /usr/local/emhttp/state/nginx.ini ]]; then
    source <(grep "NGINX_DEFAULTURL" /usr/local/emhttp/state/nginx.ini || true)
    LINK="${NGINX_DEFAULTURL}${LINK}"
  fi
fi
_expander(){ local raw="$1"; local with_escapes; with_escapes="$(echo -e "$raw")"; eval "echo \"$with_escapes\""; }
[[ "${DESCRIPTION}" == "No description" ]] && DESCRIPTION=""
DEFAULT_BODY="$(printf "%s\n\n%s\n%s" "$DESCRIPTION" "$CONTENT" "$LINK")"
FINAL_TITLE="$(_expander "${TITLE:-$SUBJECT}")"
FINAL_MESSAGE="$(_expander "${MESSAGE:-$DEFAULT_BODY}")"
case "${IMPORTANCE}" in alert) IMP_PREFIX="(ALERT) ";; warning) IMP_PREFIX="(WARN)  ";; *) IMP_PREFIX="";; esac
FINAL_TITLE="${IMP_PREFIX}${FINAL_TITLE}"
if [[ -z "${API_KEY}" ]]; then
  echo "Missing Join API key; set it in Settings → Notifications → Agents → Join." >>"$LOG"
  logger -t "$SCRIPTNAME" -- "Join: Missing API key"; exit 1; fi
DEVICE="${DEVICE_ID:-group.all}"
JOIN_URL="https://joinjoaomgcd.appspot.com/_ah/api/messaging/v1/sendPush"
TITLE_ENC=$(echo -ne "$FINAL_TITLE"); BODY_ENC=$(echo -ne "$FINAL_MESSAGE")
MAX=3
for ((i=1;i<=MAX;i++)); do
  ret=$(curl -s -k -G --data-urlencode "title=${TITLE_ENC}" --data-urlencode "text=${BODY_ENC}" -d "deviceId=${DEVICE}" -d "apikey=${API_KEY}" "${JOIN_URL}" 2>&1)
  if echo "$ret" | grep -q '"success": *true'; then exit 0; fi
  { date; echo "attempt $i of $MAX failed"; echo "$ret"; } >>"$LOG"
  (( i < MAX )) && sleep 1
done
logger -t "$SCRIPTNAME" -- "Join: Failed sending notification"; exit 1
    ]]>
  </Script>
</Agent>
]]>
  </FILE>

  <!-- On install/upgrade, copy into RAM location Dynamix reads -->
  <FILE Run="/bin/bash">
<![CDATA[
mkdir -p /usr/local/emhttp/plugins/dynamix/agents
cp -f /boot/config/plugins/dynamix/agents/Join.xml /usr/local/emhttp/plugins/dynamix/agents/Join.xml
# ensure notifications/agents dir exists (script gets materialized here by Dynamix)
mkdir -p /boot/config/plugins/dynamix/notifications/agents
echo "Join agent installed."
]]>
  </FILE>

  <!-- On remove, clean up RAM copy but leave flash copy unless forced -->
  <FILE Run="/bin/bash" Method="remove">
<![CDATA[
rm -f /usr/local/emhttp/plugins/dynamix/agents/Join.xml
echo "Join agent removed (flash copy preserved at /boot/config/plugins/dynamix/agents/Join.xml)."
]]>
  </FILE>
</PLUGIN>

---

3) (Optional) Join.sh standalone

This mirrors your existing working file (kept for completeness). If you didn’t already have it, drop it at:
/boot/config/plugins/dynamix/notifications/agents/Join.sh

#!/bin/bash
##########
API_KEY="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
TITLE="${SUBJECT:-$TITLE}"
MESSAGE="${DESCRIPTION:-$MESSAGE}"
##########
TITLE=$(echo -e "$TITLE")
MESSAGE=$(echo -e "$MESSAGE")
curl -s -k -G \
  -d "apikey=$API_KEY" \
  --data-urlencode "title=$TITLE" \
  --data-urlencode "text=$MESSAGE" \
  -d "deviceId=group.all" \
  https://joinjoaomgcd.appspot.com/_ah/api/messaging/v1/sendPush 2>&1

---

Install & test...

1. Install the plugin

• Copy join-agent.plg to /boot/config/plugins/join-agent.plg.

• From Unraid:

  • Plugins → Install Plugin → Install from disk, select the file; or

  • SSH: installplg /boot/config/plugins/join-agent.plg

2. Configure

• Go to Settings → Notifications → Agents → Join.

• Paste your API Key.

• Leave Device Id as group.all or set a specific deviceId.

• (Optional) Tweak Title/Message fields—defaults already expand $SUBJECT, $DESCRIPTION, $CONTENT, $LINK.

3. Send a test

• Click Notifications → Test (or):

/usr/local/emhttp/webGui/scripts/notify \
  -e "Join Test" -s "Unraid → Join 

✅

" \ -d "This is a test notification from $(hostname)." \ -m "Body via CONTENT" -i "warning" -l "/Dashboard"

If anything fails, check:

/var/log/notify_Join

---

Please test...

Created and moved all 3 files to the appropriate locations. Tried doing the Install Plugin and was getting an error saying the XML does not exist or xml parse error:

I then rebooted unraid and the plugin disappeared from the /boot/config/plugins/ folder. Re-copied join-agent.plg to the plugins folder. Tried to re-install the plugin and get the same error as above. I even tried copying the XML to /usr/local/emhttp/plugins/dynamix/agents/Join.xml

Nothing appears to exist at /var/log/notify_Join

No worries on trying to get this to work. I've transitioned over to Telegram to centralize and organize my unraid and related notifications better. If you want me to keep testing though I can. Thanks for trying to help.

Edited November 6, 2025Nov 6 by kimocal

I would love if you could still test this. That's fine if you moved on.

I need to make a few edits. Another. I forgot to even test a reboot and I'll need to change file location stuff.

As the best I can do is begin it to install and show what it should do but actually tested to make sure it makes its edits and response to the joint agents. Something out of scoop for me cuz I can't seem to figure out that website to create a account to get a joint API and test.

How did this topic go from asking about a removed feature and potentially asking for it to be reintroduced by the Limetech Dev team from a previous build to using AI to vibe code a solution to recreate the wheel??

Respectfully, I know you're trying to help but without the Dev team contributing to the conversation, outside of creating a plug-in to sideload the feature, I'm not sure there's a conversation to be had. Join works well, and I never had an issue with it, but I'll probably move on to an Unraid supported mechanism if it has been dropped.

As for flexing, some Dev muscles to create a plug-in for the community, more power to you. I'm not sure there's a need for this one as only two of us users have commented on this and it's probably been removed for a while, so the reach will be fairly minimal. Join as an Android application and service seems to be in maintenance mode, and that is being generous. There's no reason for active development by the Join Dev since it has worked the same since Android v10, but the last Android app update was in June 2024.

@limetech @ljm42 @SpencerJ Thoughts on the OP? Was this agent removed for a reason? Just looking for some clarification since I didn't see anything in any change logs.

1 hour ago, JesterEE said:

How did this topic go from asking about a removed feature and potentially asking for it to be reintroduced by the Limetech Dev team from a previous build to using AI to vibe code a solution to recreate the wheel??

Respectfully, I know you're trying to help but without the Dev team contributing to the conversation, outside of creating a plug-in to sideload the feature, I'm not sure there's a conversation to be had. Join works well, and I never had an issue with it, but I'll probably move on to an Unraid supported mechanism if it has been dropped.

As for flexing, some Dev muscles to create a plug-in for the community, more power to you. I'm not sure there's a need for this one as only two of us users have commented on this and it's probably been removed for a while, so the reach will be fairly minimal. Join as an Android application and service seems to be in maintenance mode, and that is being generous. There's no reason for active development by the Join Dev since it has worked the same since Android v10, but the last Android app update was in June 2024.

@limetech @ljm42 @SpencerJ Thoughts on the OP? Was this agent removed for a reason? Just looking for some clarification since I didn't see anything in any change logs.

becasue your in a genral support post and not a bug report nor comunicated to teh Devs the issue at hand...

... does no one read teh license agrements, post heders or anouncments?!!!

go make a dam bug report:
https://forums.unraid.net/bug-reports/stable-releases/