Notification Bots Configuration Guide
FlashDuty supports multiple notification channels, including SMS, email, voice calls, and various instant messaging platforms. This document provides detailed instructions for configuring each type of notification channel.
1. Notification Channels Overview
1.1 Traditional Communication Channels
SMS, Voice, Email
Notification Type | Alibaba Cloud Support | Tencent Cloud Support | Description |
---|
SMS | ✅ | ✅ | Support for alert and incident notifications |
Voice | ✅ | ✅ | Support for interactive acknowledgment |
Email | ✅ | ❌ | Only supported via Alibaba Cloud channel |
Important Notes:
- Before using voice/SMS/email notifications, ensure member information has bound phone numbers and email addresses
- Configure corresponding service providers in notification channels
- Voice notifications support interactive acknowledgment: press
1
after playback to acknowledge the incident
Supported IM Platforms and Bot Types
Platform Name | App Integration | Group Bot | Special Notes |
---|
Feishu/Lark | ✅ | ✅ | Full feature support |
Dingtalk | ✅ | ✅ | Full feature support |
WeCom | ✅ | ✅ | Full feature support |
Slack | ✅ (Beta) | ✅ | Beta version |
Microsoft Teams | ✅ | ❌ | App integration only |
Telegram | ❌ | ✅ | Bot only |
Zoom | ❌ | ✅ | Bot only |
Integration Notes:
- For detailed app integration steps, refer to:
Console → Integration Center → IM Integration
- This document focuses on group bot configuration methods
2. App Integration vs Bot Integration
2.1 Feature Comparison
Comparison Dimension | App Integration | Bot Integration |
---|
Setup Complexity | Requires admin permissions to create app | Direct creation in group, simple operation |
User Experience | Support for direct card operations | Requires browser redirect for handling |
Authentication | Support for passwordless operations | Requires manual login |
Feature Completeness | Support for acknowledge, silence, close, etc. | Basic notification functionality |
Maintenance Cost | One-time setup, long-term use | Relatively simple |
2.2 Selection Recommendations
- Recommended for App Integration: If your organization requires high user experience and has appropriate admin permissions
- Suitable for Bot Integration: If you need quick deployment or cannot obtain app creation permissions
3. App Integration Configuration Guide
3.1 Feishu/Lark App Integration
Configuration Steps:
-
Install App
- Search for "FlashDuty" app in Feishu/Lark workspace
- Click install and complete login verification
- The system will automatically complete account association
-
Configure Notification Channels
- Enter FlashDuty console's
Account Center
- Add Feishu/Lark option in notification channels
- Test connection to ensure proper configuration
-
Group Chat Configuration
- Add FlashDuty app to target group chat
- Path:
Group Settings → Group Bots → Add Bot → FlashDuty
Detailed Configuration Instructions: Please refer to the WeCom Integration Guide
3.3 Dingtalk App Integration
Configuration Steps:
- Enable App
- Create or enter Dingtalk group chat
- Click
More → Cool Apps → Cool App Library
- Search and select "FlashDuty" app
- Click "Enable" to complete installation
3.4 Microsoft Teams App Integration
Configuration Steps:
-
Get App Package
- Visit
FlashDuty Integration Center → IM Integration → Microsoft Teams
- Download app package: flashduty.zip
-
Upload App
- Enter Microsoft Teams
- Navigate to
Apps → Manage your apps → Upload an app → Upload an app to your org's app catalog
- Upload the downloaded flashduty.zip file
- Set App Permissions
- Enter Microsoft Teams Admin Center
- Find FlashDuty app
- Set app visibility to "Everyone" or custom scope
- Complete App Installation
- Wait a few minutes, organization members can find the app in
Apps → Built for your org
- Associate Teams
- Add FlashDuty app to target team
- In team chat, @FlashDuty and send association command:
linkTeam xxx
- Associate Users
- In personal chat, send association command:
linkUser xxx
- Configure Notification Strategy
- In channel's escalation rule, select Microsoft Teams app
- Configure group chat or private chat notification preferences
3.5 Slack App Integration (Beta)
Configuration Steps:
-
Authorize Integration
- Visit
FlashDuty Integration Center → IM Integration → Slack → Add
- Page redirects to Slack authorization interface
- Select workspace and click "Allow"
-
Complete Configuration
- Enter data source name and save
- In escalation rule, select Slack app and target group chat
-
Private Channel Handling
- Login to Slack, in private channel select
Integrations → Add Apps
- Add FlashDuty app then refresh group chat list
4. Bot Integration Configuration Guide
4.1 Feishu/Lark Group Bot
Configuration Steps:
-
Create Custom Bot
- Enter Feishu/Lark group chat
- Open
Group Settings → Group Bots → Add Bot
- Select "Custom Bot"
-
Configure Bot Parameters
- Set bot name and description
- Configure custom keyword:
#
- Click "Add" to generate webhook URL
-
Integrate to FlashDuty
- Copy the generated webhook URL
- Add Feishu/Lark bot in FlashDuty notification channels
- Paste webhook URL and test connection
Configuration Steps:
-
Create Group Bot
- Enter WeCom group chat
- Click
Top-right Settings → Add Group Bot → Create New Bot
-
Configure and Get Webhook
- Set bot name
- Click "Add Bot"
- Copy the generated webhook URL
-
Configure FlashDuty
- Select WeCom bot in notification channels
- Paste webhook URL
4.3 Dingtalk Group Bot
Configuration Steps:
-
Create Custom Bot
- Enter Dingtalk group chat
- Open
Group Settings → Group Management → Smart Group Assistant
- Click "Add Bot" → Select "Custom" type
-
Configure Security Settings
- Set bot name
- Add keyword:
#
- Agree to related terms
-
Complete Integration
- Copy the generated webhook URL
- Configure Dingtalk bot in FlashDuty
4.4 Telegram Bot
Configuration Steps:
-
Create Telegram Bot
- Open BotFather, send
/newbot
command
- Enter bot name
- Record the returned Token (format:
64533289xx:AAFxCAdxx_xssbnSxE6Y8mTcOBT5rxxxxx
)
-
Create Channel
- Click top-left settings → New Channel
- Create new Channel
- Add bot as Channel member
-
Get Chat ID
- In browser, visit:
https://api.telegram.org/bot{Token}/getUpdates
- Replace
{Token}
with the Token from step 1
- Get Chat ID from the returned result (starts with
-
)
4.5 Slack Bot
Configuration Steps:
-
Create Slack App
-
Enable Incoming Webhook
- In app settings page select "Incoming Webhook"
- Enable "Activate Incoming Webhooks" toggle
-
Get Webhook URL
- Click "Add New Webhook to Workspace"
- Select target channel and confirm
- Copy the generated Webhook URL
4.6 Zoom Bot
Configuration Steps:
- Create Zoom Bot
- Open the Zoom app, go to Apps > Add Apps, search for and add the Incoming Webhook app.
- Return to the chat interface and confirm that the Incoming Webhook app has been successfully added.
- In any channel or within the Incoming Webhook app, enter the command: /inc connect flashduty. The system will return the app connection information.
- Configure Flashduty
- To enable the @mention feature
- The administrator should obtain user user_id values from the Zoom admin console.
- In the Flashduty Integration Center, create a mapping table with the source label set key to email value to Flashduty Members email and the result label set to zoom_jid value to Zoom user_id.
- In the workspace’s escalation policy, associate the corresponding Zoom robot and mapping table.
5. Frequently Asked Questions
Q: Do I need to login every time when using app card messages?
A: No. Once member accounts are associated with app accounts, passwordless login is possible.
Association method:
- Search for FlashDuty app in corresponding platform
- Click app and complete login
- System will automatically establish account association
Q: What if I can't find FlashDuty app in Dingtalk/Feishu/WeCom workspace?
A: Please follow these steps to resolve:
- Check app status: Confirm FlashDuty app is enabled in your organization
- Permission check: Contact administrator to confirm you have permission to view and use the app
- Search method: Try different keywords like "FlashDuty", "Flashcat", etc.
- Contact support: If still can't find, please contact technical support for assistance
Q: Bot message sending failed, how to troubleshoot?
A: Please follow these troubleshooting steps:
- Verify Webhook address: Confirm copied Webhook address is complete and correct
- Check keyword settings: For platforms requiring keywords, ensure message template includes corresponding keywords
- Network connection: Confirm FlashDuty server can access target platform
- Permission check: Confirm bot has permission to send messages in target group
- View logs: Check detailed error logs in FlashDuty console
Q: How to customize notification message templates?
A: You can configure in FlashDuty console notification template settings:
- Enter
Configuration Management → Notification Templates
- Select corresponding notification channel type
- Edit message template, supporting variables and Markdown format
- Test template effects and save
Note: If using custom templates, ensure they include keywords required by bot platforms
Technical Support: If you encounter configuration issues or need further assistance, please contact FlashDuty technical support team.