Notifications
Configure notifications from your Junet instance
Enable Email Notifications
- Go to Admin → Application settings → Notifications
- Find the Email Configuration section
- Toggle Enable Email Notifications to ON
- This allows Junet to send notifications via email
Email Provider
SMTP is the standard email delivery service for sending notifications.
- Email Provider: Select SMTP from the dropdown
- This configures your mail server connection
SMTP Settings
Configure your SMTP server details to enable email delivery:
SMTP Host
- Enter your SMTP server address
- Example:
smtp.example.com - This is your email server's hostname
SMTP Port
- Enter the port number for your SMTP server
- Common ports:
587- Standard SMTP with STARTTLS (recommended)465- SMTP with SSL/TLS25- Plain SMTP (not recommended for production)
- Default:
587
Use TLS/SSL
- Toggle to enable secure connection
- Recommended: Enabled for production environments
- Encrypts email transmission for security
SMTP Username
- Enter your email server authentication username
- Usually your full email address
- Example:
notifications@example.com
SMTP Password
- Enter your email server authentication password
- Use app-specific passwords when available
- Kept secure and encrypted
Email Identity
Configure the sender information for outgoing notifications:
From Email
- The email address notifications are sent from
- Example:
notifications@example.com - Must be a valid email address on your domain
- This appears in the "From" field
From Name
- The display name for the sender
- Example:
Junet Notifications - This appears alongside the email address
- Make it recognizable for your users
Test Email Configuration
Before relying on email notifications, verify your configuration works:
- Complete all SMTP settings above
- Click Test Email Configuration
- Check the configured email inbox
- You should receive a test notification
- If the test fails, verify your SMTP credentials and settings
Using Gmail? Enable 2-factor authentication and create an App Password instead of using your regular password.
Firewall Configuration: Ensure your server can reach your SMTP host on the configured port. Some cloud providers block outbound port 25 by default.
Webhook Configuration
Set up webhook endpoints to receive real-time notifications via HTTP callbacks.
Enable Webhook Notifications
- Go to Admin → Application settings → Notifications
- Scroll to the Webhook Configuration section
- Toggle Enable Webhook Notifications to ON
- This allows Junet to send notifications via webhook
Webhook URL
Configure the endpoint that will receive notifications:
- Enter the full HTTPS URL of your webhook endpoint
- Example:
https://your-server.com/webhooks/notifications - This endpoint will receive HTTP POST requests with notification data
- Must be publicly accessible or accessible from your Junet instance
Your webhook endpoint should accept POST requests and return a 2xx status code to acknowledge receipt.
Webhook Secret (Optional)
Add security to your webhook with signature verification:
- Enter a secret key for HMAC signature verification
- This is used to sign webhook payloads
- Recommended for production environments
- Verify the
X-Webhook-Signatureheader in incoming requests - Uses HMAC-SHA256 algorithm
Example verification (Node.js):
const crypto = require('crypto');
function verifyWebhookSignature(payload, signature, secret) {
const hmac = crypto.createHmac('sha256', secret);
const digest = hmac.update(payload).digest('hex');
return signature === digest;
}Test Webhook Configuration
Verify your webhook endpoint is working correctly:
- Complete the Webhook URL field
- Optionally add a Webhook Secret
- Click Send Test Webhook
- Check your webhook endpoint logs
- You should receive a test notification payload
- Verify the signature if you configured a secret
Testing Webhooks Locally? Use tools like ngrok or localtunnel to expose your local server to the internet during development.
Notification Flows
Configure when and how notifications are sent based on system events.
Service Down Alert
Get notified immediately when a service becomes unavailable:
- Event: Service Down
- Trigger: When a service becomes unavailable
- Use Case: Critical for monitoring uptime
- Toggle: Enable/disable this notification flow
- Recommended: Enabled for production environments
What triggers this:
- Connection failures to configured services
- API endpoints becoming unreachable
- Database connection issues
- External service timeouts
Service Recover Alert
Know when services come back online:
- Event: Service Recover
- Trigger: When a service comes back online
- Use Case: Confirm issues are resolved
- Toggle: Enable/disable this notification flow
- Recommended: Enabled to track recovery times
What triggers this:
- Previously unavailable services become reachable
- Successful reconnection after downtime
- Health checks passing after failures
Embedding Complete
Track when document embedding processes finish:
- Event: Embedding Finished
- Trigger: When document embedding completes
- Use Case: Monitor indexing progress for large document sets
- Toggle: Enable/disable this notification flow
- Recommended: Enabled for tracking data ingestion
What triggers this:
- Completion of document vectorization
- Successful indexing of new documents
- Batch embedding jobs finishing
Error Threshold Exceeded
Get alerted when error rates spike:
- Event: Error Threshold Exceeded
- Trigger: When error rate is too high
- Use Case: Detect system issues early
- Toggle: Enable/disable this notification flow
- Recommended: Enabled for proactive monitoring
What triggers this:
- Error rate exceeding configured thresholds
- Multiple failed requests within a time window
- System-wide error patterns detected
- Critical exceptions being thrown repeatedly
Best Practice: Enable all notification flows in production environments. You can always filter or route notifications at your email or webhook endpoint level.