Configure email, Teams, Telegram, NTFY.SH, and webhook notifications for your events
To enable email notifications, you need to configure the SMTP settings and define recipients. You can specify which tenants should send event notifications and filter notifications by event severity directly within the sensors. Additionally, in each sensor and other relevant features, you have the option to refine the conditions under which an event notification should be triggered.
This field represents the username of your email account, for example: noreply@netlockrmm.com
Your SMTP password
Your SMTP server
Your SMTP port
Depending on your email server's configuration, you may need to enable SSL/TLS for secure communication
To verify that your configuration is correct, use the "Test" button. If the test is successful, you'll see a confirmation message and receive a test email.
The recipient's email address
For your internal purposes
Notifications will only be sent if an event meets the defined severity level
Select the tenants from which you want to receive event notifications
In the left menu bar, scroll down to Notifications and select E-Mail
Click SMTP Settings and enter your SMTP credentials. Test the connection to ensure your configuration is correct
Click the Add button located to the left of the SMTP Settings button
Enter the email address where you want to receive alerts
Provide a description for easier identification
Choose the severity level you want to receive alerts for
If you want to receive alerts for devices that go offline, enable Uptime Monitoring
Drag the tenants you want to receive notifications for into the Selected Tenants section
Click Save to apply your configuration
To enable Microsoft Teams notifications, you'll need to set up connectors. For instructions on creating an incoming webhook connector, refer to Microsoft's documentation:
Your connector's name for internal purposes
The webhook URL of your connector
For your internal purposes
Notifications will only be sent if an event meets the defined severity level
Select the tenants from which you want to receive event notifications
To enable Telegram notifications, you'll need to set up a Telegram Bot. For instructions refer to Telegram's documentation:
Your bot's name for internal purposes
The bot's token/API key
The ID of the chat you want to receive the messages to
Notifications will only be sent if an event meets the defined severity level
Select the tenants from which you want to receive event notifications
To enable NTFY.SH notifications, you'll need to set up a topic URL and optionally an access token. For instructions refer to NTFY.SH documentation:
Your topic's name for internal purposes
The topic's URL
If required, you can add your access token here
Notifications will only be sent if an event meets the defined severity level
Select the tenants from which you want to receive event notifications
To enable Webhook notifications, you need to configure a webhook URL, HTTP method, request body, and optionally request headers.
You can use the following variables in your request body to include dynamic event information:
$netlock_tenant_name
$netlock_location_name
$netlock_device_name
$netlock_date
$netlock_reported_by
$netlock_event
$netlock_descriptionThese variables will be automatically replaced with actual values when the webhook is triggered:
• $netlock_tenant_name – The name of the tenant where the event occurred
• $netlock_location_name – The location associated with the device or event
• $netlock_device_name – The name of the device that triggered the event
• $netlock_date – The exact date and time when the event occurred
• $netlock_reported_by – The event type that reported the event
• $netlock_event – The type or category of the event that occurred
• $netlock_description – A detailed description of the event, if available
Your webhook's name for internal purposes
Optional description of the webhook's purpose
The webhook endpoint URL (e.g., https://example.com/webhook)
HTTP method to use (GET, POST, PUT, DELETE, PATCH)
JSON payload to send (can include variables)
Custom HTTP headers (e.g., Content-Type, Authorization)
Notifications will only be sent if an event meets the defined severity level
Select the tenants from which you want to receive event notifications
If enabled and Disconnection Alert is active in the device overview, the event will be forwarded
{
"tenant": "$netlock_tenant_name",
"device": "$netlock_device_name",
"event": "$netlock_event",
"timestamp": "$netlock_date",
"message": "Alert from device $netlock_device_name in tenant $netlock_tenant_name"
}{
"Content-Type": "application/json",
"Authorization": "Bearer your-token-here"
}Use the "Test Webhook" button to verify your configuration before saving. This will send a test request to your webhook endpoint and display the response status.