netalertx · jokob-sk · Sep 3, 2026 · Sep 3, 2026 · Sep 5, 2026 · Sep 5, 2026
diff --git a/docs/COMMON_ISSUES.md b/docs/COMMON_ISSUES.md
@@ -117,7 +117,7 @@ Slowness can be caused by:
 
 With `ARPSCAN` scans some devices might flip IP addresses after each scan triggering false notifications. This is because some devices respond to broadcast calls and thus different IPs after scans are logged.
 
-See how to prevent IP flipping in the [ARPSCAN plugin guide](/server/plugins/arp_scan/README.md).
+See how to prevent IP flipping in the [ARPSCAN plugin guide](https://github.com/netalertx/NetAlertX/blob/main/server/plugins/arp_scan/README.md).
 
 Alternatively adjust your [notification settings](./NOTIFICATIONS.md) to prevent false positives by filtering out events or devices.
 

diff --git a/docs/CUSTOM_PROPERTIES.md b/docs/CUSTOM_PROPERTIES.md
@@ -35,10 +35,11 @@ Visible properties (`CUSTPROP_show: true`) are displayed as interactive icons in
    - Manage devices with actions like delete.
    - Example: Quickly remove a device from the network.
 
-4. **Plugins**:
+4. **Plugins (Experimental 🧪)**:
 
-   - Future placeholder for running custom plugin scripts.
-   - **Note**: Not implemented yet.
+   - Manually trigger an on-demand run of a plugin, regardless of its configured `RUN` schedule.
+   - Example: Add a button to re-run a scan-type plugin like `NMAPDEV` on demand.
+   - **Note**: The plugin runs with whatever settings/params it already has configured - it is not passed any device-specific or ad-hoc arguments. Some plugins require settings (credentials, target host, subnet, etc.) to be configured before they'll run properly; triggering an unconfigured plugin this way may fail or do nothing useful.
 
 ---
 
@@ -56,6 +57,10 @@ Visible properties (`CUSTPROP_show: true`) are displayed as interactive icons in
 
    - Enable device removal functionality using `CUSTPROP_type: delete_dev`.
 
+4. **Run a Plugin On Demand (Experimental 🧪)**:
+
+   - Use `CUSTPROP_type: run_plugin` with `CUSTPROP_args` set to the target plugin's unique prefix (e.g. `NMAPDEV`) to add a button that triggers that plugin immediately. Make sure the plugin's own settings (credentials, target host, subnet, etc.) are already configured, since none are passed in via this action.
+
 ---
 
 ## Defining Custom Properties
@@ -66,28 +71,45 @@ Custom properties are structured as a list of objects, where each property inclu
 |--------------------|-----------------------------------------------------------------------------|
 | `CUSTPROP_icon`    | The icon (Base64-encoded HTML) displayed for the property.                 |
 | `CUSTPROP_type`    | The action type (e.g., `show_notes`, `link`, `delete_dev`).                |
-| `CUSTPROP_name`    | A short name or title for the property.                                    |
-| `CUSTPROP_args`    | Arguments for the action (e.g., URL or modal text).                        |
+| `CUSTPROP_name`    | A short name or title for the property. Supports `{{fieldName}}` wildcards. |
+| `CUSTPROP_args`    | Arguments for the action (e.g., URL or modal text). Supports `{{fieldName}}` wildcards. |
 | `CUSTPROP_notes`   | Additional notes or details displayed when applicable.                    |
 | `CUSTPROP_show`    | A boolean to control visibility (`true` to show on the listing page).      |
 
 ---
 
+## Wildcards in `CUSTPROP_name` / `CUSTPROP_args`
+
+`CUSTPROP_name` and `CUSTPROP_args` are resolved per-device before rendering, so you can reference any of that device's own fields with `{{fieldName}}` - field names are matched case-insensitively, so `{{devLastIp}}` and `{{devLastIP}}` are equivalent. If a field name doesn't exist, the placeholder is left as-is (e.g. `{{devTypo}}` stays visible) rather than silently disappearing, to make a typo obvious while you're setting one up.
+
+This is what makes a single `link`/`link_new_tab` custom property work across every device rather than one URL per device - e.g. to jump to a device's traffic log in an AdGuard Home instance, filtered to that device's IP:
+
+```
+CUSTPROP_type: link_new_tab
+CUSTPROP_args: http://my_adguard_url/#logs?search={{devLastIP}}
+```
+
+This same property definition can be reused two ways: set directly on a single device (affecting that device alone), or set once via the `NEWDEV_devCustomProps` setting, which becomes the default `devCustomProps` for devices discovered *after* the setting is saved. It is not applied retroactively - existing devices keep their current `devCustomProps` and need to be updated individually (or reset via the device's "reset properties" action) to pick up a changed default.
+
+Commonly useful fields: `devMac`, `devLastIP`, `devName`, `devVendor`, `devType`, `devGUID`.
+
+---
+
 ## Available Action Types
 
 - **Show Notes**: Displays a modal with a title and additional notes.
   - **Example**: Show firmware details or custom messages.
 - **Link**: Redirects to a specified URL in the current browser tab. (**Arguments** Needs to contain the full URL.)
 - **Link (New Tab)**: Opens a specified URL in a new browser tab. (**Arguments** Needs to contain the full URL.)
 - **Delete Device**: Deletes the device using its MAC address.
-- **Run Plugin**: Placeholder for executing custom plugins (not implemented yet).
+- **Run Plugin (Experimental 🧪)**: Triggers an on-demand run of the plugin named in **Arguments** (its unique prefix, e.g. `NMAPDEV`), regardless of that plugin's configured `RUN` schedule.
 
 
 ---
 
 ## Notes
 
-- **Plugin Functionality**: The `run_plugin` action type is currently not implemented and will show an alert if used.
+- **Plugin Functionality (Experimental 🧪)**: `run_plugin` requires `CUSTPROP_args` to exactly match an enabled plugin's unique prefix (as listed in the `LOADED_PLUGINS` setting); an unrecognized or disabled prefix is rejected by the backend. It simply re-runs the plugin with its existing configuration - some plugins need required settings/params (e.g. credentials, target host, subnet) filled in first, or the run will fail or silently do nothing. Marked experimental until this is more clearly surfaced in the UI.
 - **Custom Icons (Experimental 🧪)**: Use Base64-encoded HTML to provide custom icons for each property. You can add your icons in Setttings via the `CUSTPROP_icon` settings
 - **Visibility Control**: Only properties with `CUSTPROP_show: true` will appear on the listing page.
 

diff --git a/docs/INITIAL_SETUP.md b/docs/INITIAL_SETUP.md
@@ -25,7 +25,7 @@ Get **NetAlertX** up and running in a few simple steps.
 
 > [!NOTE]
 > Configure your SMTP settings or enable additional `▶️ publisher` plugins to send alerts.
-> For more flexibility, try [📚 `_publisher_apprise`](/server/plugins/_publisher_apprise/), which supports over 80 notification services.
+> For more flexibility, try [📚 `_publisher_apprise`](https://github.com/netalertx/NetAlertX/tree/main/server/plugins/_publisher_apprise/), which supports over 80 notification services.
 
 ---
 

diff --git a/docs/PERFORMANCE.md b/docs/PERFORMANCE.md
@@ -39,14 +39,14 @@ Two plugins help maintain the system’s performance:
 ### **1. Database Cleanup (DBCLNP)**
 
 * Handles database maintenance and cleanup.
-* See the [DB Cleanup Plugin Docs](/server/plugins/db_cleanup/README.md).
+* See the [DB Cleanup Plugin Docs](https://github.com/netalertx/NetAlertX/tree/main/server/plugins/db_cleanup/README.md).
 * Ensure it’s not failing by checking logs.
 * Adjust the schedule (`DBCLNP_RUN_SCHD`) and timeout (`DBCLNP_RUN_TIMEOUT`) if necessary.
 
 ### **2. Maintenance (MAINT)**
 
 * Cleans logs and performs general maintenance tasks.
-* See the [Maintenance Plugin Docs](/server/plugins/maintenance/README.md).
+* See the [Maintenance Plugin Docs](https://github.com/netalertx/NetAlertX/tree/main/server/plugins/maintenance/README.md).
 * Verify proper operation via logs.
 * Adjust the schedule (`MAINT_RUN_SCHD`) and timeout (`MAINT_RUN_TIMEOUT`) if needed.
 

diff --git a/docs/PLUGINS_DEV_DATA_CONTRACT.md b/docs/PLUGINS_DEV_DATA_CONTRACT.md
@@ -18,7 +18,7 @@ Plugins communicate with NetAlertX by writing results to a **pipe-delimited log
 
 ## Using `plugin_helper.py`
 
-The easiest way to ensure correct output is to use the [`plugin_helper.py`](../server/plugins/plugin_helper.py) library:
+The easiest way to ensure correct output is to use the [`plugin_helper.py`](https://github.com/netalertx/NetAlertX/blob/main/server/plugins/plugin_helper.py) library:
 
 ```python
 from plugin_helper import Plugin_Objects