Managing Channels
Create and manage webhook notification channels for Slack, Teams, and Discord directly from the dashboard. Notification Channels let you configure...
Managing Notification Channels
Create and manage webhook notification channels for Slack, Teams, and Discord directly from the dashboard.
Overview
Notification Channels let you configure webhook-based alerts to receive security notifications in your team's communication platforms. Unlike OAuth integrations, webhook channels give you full control over which channels receive notifications.
Supported Platforms:
- Slack (via Incoming Webhooks)
- Microsoft Teams (via Connectors)
- Discord (via Webhooks)
Accessing Notification Channels
- Log in to BlockSecOps
- Navigate to Admin → Notifications in the sidebar
- Or go directly to
/notification-channels
Note: Notification Channels require a Startup tier subscription or higher.
Dashboard Overview
The Notification Channels page displays:
Stats Cards
| Card | Description |
|---|---|
| Total Channels | Number of configured channels |
| Active | Channels currently receiving notifications |
| Delivered | Total successful notifications sent |
| Failed | Total failed delivery attempts |
Channels Table
Each channel row shows:
- Channel icon: Slack, Teams, or Discord brand icon
- Name: Your channel name
- Events: Subscribed event types (with badge overflow)
- Deliveries: Success/failed counts
- Status: Active or Paused badge
- Actions: Test, History, Edit, Delete buttons
Creating a Channel
Step 1: Get Your Webhook URL
For Slack
- Go to Slack API Apps
- Create or select an app
- Navigate to Incoming Webhooks
- Activate webhooks and click Add New Webhook to Workspace
- Select the destination channel
- Copy the webhook URL
Format: https://hooks.slack.com/services/T00000000/B00000000/XXXX...
For Microsoft Teams
- Open Microsoft Teams
- Go to the target channel
- Click ... → Connectors
- Find Incoming Webhook → Configure
- Name the webhook (e.g., "BlockSecOps Alerts")
- Copy the webhook URL
Format: https://outlook.office.com/webhook/GUID/IncomingWebhook/GUID/GUID
For Discord
- Open Discord server settings
- Go to Integrations → Webhooks
- Click New Webhook
- Configure name and channel
- Copy the webhook URL
Format: https://discord.com/api/webhooks/CHANNEL_ID/TOKEN
Step 2: Create the Channel
- Click Add Channel on the Notification Channels page
- Select channel type: Click the Slack, Teams, or Discord icon
- Enter name: A descriptive name (e.g., "Security Alerts - #dev-team")
- Paste webhook URL: The URL you copied above
- Select events: Choose which events trigger notifications
- Set severity filter (optional): Only notify for certain severity levels
- Click Create Channel
Event Types
Select which events trigger notifications:
| Event | Description |
|---|---|
scan.completed |
Scan finished successfully |
scan.failed |
Scan encountered an error |
vulnerability.critical |
Critical severity vulnerability found |
vulnerability.high |
High severity vulnerability found |
Severity Filtering
Filter notifications by minimum severity:
| Filter | Notifications Sent |
|---|---|
| All severities | Every vulnerability notification |
| Low and above | Low, Medium, High, Critical |
| Medium and above | Medium, High, Critical |
| High and above | High, Critical only |
| Critical only | Critical vulnerabilities only |
This helps reduce noise in busy channels.
Managing Channels
Quick Status Toggle
Click the Active or Paused badge on any channel to quickly toggle its status. Paused channels don't receive notifications.
Edit a Channel
- Click the pencil icon on a channel row
- Modify settings:
- Change the name
- Update subscribed events
- Adjust severity filter
- Toggle active/inactive
- Click Save Changes
Note: Webhook URLs cannot be changed after creation. To use a different URL, delete the channel and create a new one.
Delete a Channel
- Click the trash icon on a channel row
- Review the channel details and statistics
- Click Delete Channel to confirm
⚠️ This action is permanent and cannot be undone.
Testing Channels
Verify your webhook is working:
- Click the play icon on a channel row
- Click Send Test in the modal
- Wait for the result:
- Success: Green checkmark with HTTP status and response time
- Failure: Red X with error details
- Check your Slack/Teams/Discord channel for the test message
Test Message Format
The test notification includes:
- "Test Notification from BlockSecOps" title
- Confirmation message
- Timestamp
- Link to dashboard
Viewing Delivery History
Track all notification deliveries:
- Click the clock icon on a channel row
- View summary statistics:
- Total deliveries
- Successful deliveries
- Failed deliveries
- Filter by status: All, Delivered, or Failed
- Review individual deliveries:
- Event type
- Status (success/failure icon)
- Timestamp and relative time
- HTTP status code
- Response duration
- Error message (if failed)
Message Formats
Slack Messages
Notifications use Block Kit formatting with:
- Color-coded severity (red for critical, orange for high)
- Section with vulnerability/scan details
- Action buttons linking to dashboard
Teams Messages
Notifications use Adaptive Cards with:
- Themed header color by severity
- Fact sets for details
- Action URLs for dashboard links
Discord Messages
Notifications use rich embeds with:
- Colored sidebar by severity
- Field layout for details
- Footer with timestamp
Troubleshooting
Channel Not Receiving Messages
- Check channel status: Ensure it's not paused
- Verify webhook URL: Test the channel to confirm connectivity
- Check events: Make sure desired events are selected
- Review filters: Severity filter may be blocking notifications
Test Fails with Error
| Error | Solution |
|---|---|
404 Not Found |
Webhook was deleted - create a new one |
403 Forbidden |
Channel permissions changed - regenerate webhook |
Timeout |
Platform service issue - try again later |
Invalid URL |
Webhook URL format incorrect |
Messages Not Appearing in Channel
- Slack: Ensure the webhook app is still installed
- Teams: Check the connector is still configured
- Discord: Verify the webhook wasn't deleted from server settings
Best Practices
Channel Organization
- Create separate channels for different severity levels
- Use descriptive names (e.g., "Production - Critical Alerts")
- Consider project-specific channels for large teams
Filter Strategy
- Use "Critical only" for high-traffic channels
- Use "All severities" for dedicated security channels
- Review and adjust filters as needed
Testing
- Always test new channels before relying on them
- Re-test after any platform changes
- Check delivery history regularly for failures
API Alternative
You can also manage notification channels via API:
# Create channel
curl -X POST "https://api.blocksecops.com/api/v1/notification-channels" \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "My Slack Channel",
"channel_type": "slack",
"webhook_url": "https://hooks.slack.com/services/...",
"events": ["scan.completed", "vulnerability.critical"]
}'
# List channels
curl "https://api.blocksecops.com/api/v1/notification-channels" \
-H "Authorization: Bearer YOUR_TOKEN"
# Test channel
curl -X POST "https://api.blocksecops.com/api/v1/notification-channels/{id}/test" \
-H "Authorization: Bearer YOUR_TOKEN"
See API Documentation for full details.
Next Steps
- Slack Integration - Full Slack OAuth integration
- Teams Integration - Teams setup guide
- Discord Integration - Discord setup guide
- Webhooks - Custom webhook integration