Skip to main content
The notification system automatically delivers scheduled task results via email and webhooks. Once admins pre-configure notification channels, users select a channel when creating scheduled tasks to receive result notifications.
Notification settings main screen

Notification Architecture

StageOwnerDescription
Channel setupAdminPre-configure SMTP, SendGrid, Azure Email, Slack, etc.
Channel selectionUserSpecify notification channel and trigger condition in the schedule
Notification dispatchSystemAfter 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”)
Add email channel
FieldDescription
Channel nameIdentifier name (e.g., “Default”, “Marketing Team Mail”)
Email ProviderChoose SMTP, SendGrid, Azure Email, or MS Graph

Per-Provider Settings

Connect your internal mail server or external SMTP service (Gmail, Outlook, etc.).
SettingDescriptionExample
ServerSMTP server addresssmtp.gmail.com
PortSMTP port587 (TLS) / 465 (SSL)
UsernameAuth accountnoreply@company.com
PasswordAuth password
Use TLSEnable TLS encryptionUse on port 587
Use SSLEnable SSL encryptionUse on port 465
Sender addressFrom email addressnoreply@company.com
Sender nameFrom nameCloosphere
TLS and SSL can’t be used together. Use TLS on port 587 and SSL on port 465.

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.
ResultDescription
SuccessServer connection and authentication both OK
Auth failureVerify username/password
Connection failureVerify server address, port, firewall
TimeoutVerify network connection

Send Test Email

In the Send Test Email section, enter a recipient address and click Send to verify actual email delivery.
1

Enter recipient email

Enter the address to receive the test email.
2

Click Send

Click the Send button.
3

Verify reception

Verify test email reception in the inbox (including spam folder).

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”)
Add webhook channel
FieldDescription
Channel nameIdentifier name (e.g., “Engineering Slack”)
ProviderSlack / Microsoft Teams / Discord / Telegram / Google Chat
Webhook URLReceiving 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

Generate webhook URL:
  1. Enable Incoming Webhooks in your Slack app management page
  2. Click Add New Webhook to Workspace
  3. Pick a channel and click Allow
  4. Copy the generated URL (https://hooks.slack.com/services/...)
Notification format: Header block + Fields (prompt, completion time) + Section (result) + chart image

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

ConditionDescriptionUse Case
AlwaysNotify on success and failureCritical schedule monitoring
Success onlyNotify only on successful completionRegular report delivery
Failure onlyNotify only on errorsFailure detection alerts

Multiple Notifications

A single scheduled task can have multiple notification channels.
NotificationChannelTargetCondition
Notif 1EmailTeam LeadAlways
Notif 2Slack webhookEngineering channelFailure only
Notif 3Teams webhookExecutive channelSuccess only

Chart Image Delivery

Plotly charts generated by DbSphere agents are server-side rendered to PNG images and included in notifications.
ChannelMethodDescription
EmailInline Base64Image directly embedded in body
SlackImage URLDisplayed as image block
TeamsAdaptive CardImage element in card
DiscordEmbed imageOnly first chart included
Google ChatTextSame 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

SymptomCheck
Connection failureVerify server address, port. Check firewall SMTP port allowance
Auth failureVerify username/password. Google requires app passwords
Email not receivedCheck recipient spam folder. Verify sender domain SPF/DKIM
TLS errorVerify TLS/SSL setting and port combination (587-TLS, 465-SSL)
SendGrid errorCheck API key permission. Verify sender address verified
Azure Email errorCheck Connection String validity. Verify sender provisioned in Azure
SymptomCheck
Send failureCheck webhook URL validity. Check if URL has expired
Message not shownCheck target channel/app permissions. Check if bot can access channel
TimeoutCheck network connection. Check firewall outbound HTTPS allowance
Format brokenCheck provider setting (Slack/Teams/Discord/Telegram/Google Chat selection correct)
SymptomCheck
No notificationsCheck schedule’s notification settings. Verify trigger condition correctness
No chart imageVerify the agent is connected to DbSphere