
Notification Architecture
| Stage | Owner | Description |
|---|---|---|
| Channel setup | Admin | Pre-configure SMTP, SendGrid, Azure Email, Slack, etc. |
| Channel selection | User | Specify notification channel and trigger condition in the schedule |
| Notification dispatch | System | After scheduled task runs, deliver result to selected channel |
Email Channels
Add email channels in Admin > Settings > Notifications or the dedicated notification management screen. Register multiple channels to use different sender configs per team.Add Channel
Click the + icon button on the right of the Email section. (Tooltip: “Add Email Channel”)
| Field | Description |
|---|---|
| Channel name | Identifier name (e.g., “Default”, “Marketing Team Mail”) |
| Email Provider | Choose SMTP, SendGrid, Azure Email, or MS Graph |
Per-Provider Settings
- SMTP
- SendGrid
- Azure Email
- MS Graph
Connect your internal mail server or external SMTP service (Gmail, Outlook, etc.).
| Setting | Description | Example |
|---|---|---|
| Server | SMTP server address | smtp.gmail.com |
| Port | SMTP port | 587 (TLS) / 465 (SSL) |
| Username | Auth account | noreply@company.com |
| Password | Auth password | |
| Use TLS | Enable TLS encryption | Use on port 587 |
| Use SSL | Enable SSL encryption | Use on port 465 |
| Sender address | From email address | noreply@company.com |
| Sender name | From name | Cloosphere |
Test Connection
Click the Test button to verify mail server connection.Test Connection and Send Test Email are only available in edit mode after saving the channel. When adding a new channel, save first, then reopen and test.
| Result | Description |
|---|---|
| Success | Server connection and authentication both OK |
| Auth failure | Verify username/password |
| Connection failure | Verify server address, port, firewall |
| Timeout | Verify network connection |
Send Test Email
In the Send Test Email section, enter a recipient address and click Send to verify actual email delivery.Webhook Channels
Connect with external messaging services to send notifications.Add Channel
Click the + icon button on the right of the Webhook section. (Tooltip: “Add Webhook Channel”)
| Field | Description |
|---|---|
| Channel name | Identifier name (e.g., “Engineering Slack”) |
| Provider | Slack / Microsoft Teams / Discord / Telegram / Google Chat |
| Webhook URL | Receiving webhook URL from the provider (except Telegram — see below) |
Telegram uses Bot Token and Chat ID instead of webhook URL. The input form auto-changes when Telegram is selected.
Per-Provider Settings
- Slack
- Teams
- Discord
- Telegram
- Google Chat
Generate webhook URL:
- Enable Incoming Webhooks in your Slack app management page
- Click Add New Webhook to Workspace
- Pick a channel and click Allow
- Copy the generated URL (
https://hooks.slack.com/services/...)
Test Webhook
Click Test Webhook to send a test message in the selected provider’s format.Test Webhook is only available in edit mode after saving the channel.
Schedule Notification Integration
After admins configure channels, users configure notifications in scheduled tasks.Trigger Conditions
| Condition | Description | Use Case |
|---|---|---|
| Always | Notify on success and failure | Critical schedule monitoring |
| Success only | Notify only on successful completion | Regular report delivery |
| Failure only | Notify only on errors | Failure detection alerts |
Multiple Notifications
A single scheduled task can have multiple notification channels.| Notification | Channel | Target | Condition |
|---|---|---|---|
| Notif 1 | Team Lead | Always | |
| Notif 2 | Slack webhook | Engineering channel | Failure only |
| Notif 3 | Teams webhook | Executive channel | Success only |
Chart Image Delivery
Plotly charts generated by DbSphere agents are server-side rendered to PNG images and included in notifications.| Channel | Method | Description |
|---|---|---|
| Inline Base64 | Image directly embedded in body | |
| Slack | Image URL | Displayed as image block |
| Teams | Adaptive Card | Image element in card |
| Discord | Embed image | Only first chart included |
| Google Chat | Text | Same text payload as Slack |
Chart images are auto-extracted before notification dispatch. Chart markers are removed from the notification body so clean text is delivered.
Troubleshooting
Email issues
Email issues
| Symptom | Check |
|---|---|
| Connection failure | Verify server address, port. Check firewall SMTP port allowance |
| Auth failure | Verify username/password. Google requires app passwords |
| Email not received | Check recipient spam folder. Verify sender domain SPF/DKIM |
| TLS error | Verify TLS/SSL setting and port combination (587-TLS, 465-SSL) |
| SendGrid error | Check API key permission. Verify sender address verified |
| Azure Email error | Check Connection String validity. Verify sender provisioned in Azure |
Webhook issues
Webhook issues
| Symptom | Check |
|---|---|
| Send failure | Check webhook URL validity. Check if URL has expired |
| Message not shown | Check target channel/app permissions. Check if bot can access channel |
| Timeout | Check network connection. Check firewall outbound HTTPS allowance |
| Format broken | Check provider setting (Slack/Teams/Discord/Telegram/Google Chat selection correct) |
General issues
General issues
| Symptom | Check |
|---|---|
| No notifications | Check schedule’s notification settings. Verify trigger condition correctness |
| No chart image | Verify the agent is connected to DbSphere |
