Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. IM integration
  • Getting Started
    • Introduction
    • Quick start
    • FAQ
    • Product Comparison
  • Incidents
    • What is an Incident
    • View Incidents
    • Handle Incidents
    • Escalations and Assignments
    • Custom Fields
    • Custom Actions
    • Alert Noise Reduction
    • Past Incidents
    • Outlier Incidents
  • Configure Flashduty
    • Channels
    • Integrate Alerts
    • Alert Noise Reduction
    • Escalation Rules
    • Label Enrichment
    • Schedules
    • Templates
    • Service Calendars
    • Preferences
    • Alert Routing
    • Silence and Inhibition
    • Filters
    • Notification Bots
    • Alert Pipeline
  • Platform
    • Teams and Members
    • Permissions
    • Single Sign-On
    • Insights
  • Advanced Features
    • Referencing Variables
    • Dynamic Assignment
  • Integrations
    • Alerts integration
      • Standard Alert Integration
      • Email Integration
      • Nightingale/FlashCat Integration
      • Prometheus Integration
      • Grafana Integration
      • Zabbix Integration
      • Uptime Kuma Integration
      • Alibaba Cloud ARMS Integration
      • Alibaba Cloud Monitor CM Event Integration
      • Alibaba Cloud Monitor CM Metrics Integration
      • Alibaba Cloud SLS Integration
      • AWS CloudWatch Integration
      • Azure Monitor Integration
      • Baidu Cloud BCM Integration
      • Huawei Cloud CES Integration
      • Influxdata Integration
      • Open Falcon Integration
      • PagerDuty Integration
      • Tencent BlueKing Integration
      • Tencent Cloud CLS Integration
      • Tencent Cloud Monitor CM Integration
      • Tencent Cloud EventBridge
      • OceanBase Integration
      • Graylog Integration
      • Skywalking Integration
      • Sentry Integration
      • Jiankongbao Integration
      • AWS EventBridge Integration
      • Dynatrace Integration
      • Huawei Cloud LTS Integration
      • GCP Integration
      • Splunk Alert Events Integration
      • AppDynamics Alert Integration
      • SolarWinds Alert Events Integration
      • Volcengine CM Alert Events Integration
      • Volcengine CM Event Center Integration
      • Volcengine TLS Integration
      • OpManager Integration
      • Meraki Integration
      • Keep Integration
      • ElastAlert2 Alert Integration
      • StateCloud Alert Events
      • Guance Alert Events
      • Zilliz Alert Events
      • Huawei Cloud APM Alerts
      • zstack integration
    • Change integration
      • Standard Change Event
      • Jira Issue Events
    • IM integration
      • Feishu (Lark) Integration Guide
      • Dingtalk Integration
      • WeCom Integration
      • Slack Integration
      • Microsoft Teams Integration
    • Single Sign-On
      • Authing Integration
      • Keycloak Guide
      • OpenLDAP Guide
    • Webhooks
      • Alert webhook
      • Incident webhook
      • Costom action
  • Terms
    • Terms of Service
    • User Agreement/Privary Policy
    • SLA
    • Data Security
  1. IM integration

Feishu (Lark) Integration Guide

Integrate with Feishu(Lark) custom application to receive and respond to alerts within Feishu/Lark.

I. Create Feishu/Lark Application#


1. Create Custom Application#

Visit Feishu/Lark Developer Console to create an internal custom application. (For details, see Feishu/Lark development documentation - Create Enterprise Custom Application)
drawing
You can use the Flashduty official icon as the application icon.

2. Copy Credentials#

Go to the Credentials & Basic Info page, copy the App ID and App Secret for later use.
drawing

3. Copy Event Callback Token Information#

Go to Development Configuration - Events & Callbacks - Encryption Configuration page, copy the Encrypt Key (recommended for better security) and Verification Token for later use.
drawing

II. Add Feishu/Lark Integration#


Return to Flashduty Integration Center page, select Instant Messaging => Feishu/Lark, fill in the Name and the previously copied App ID, App Secret, Verification Token, and Encrypt Key, then click save to create.
drawing
After creation, you'll see the newly added Feishu/Lark integration in the list. Click on the name to enter details, where you'll find the Web Configuration URL, Redirect URL, and Message Card Request URL information, which will be used in later steps.
drawing

III. Configure Feishu/Lark Application#


1. Enable and Configure Application Capabilities#

1). Return to the Feishu/Lark Developer Console, enter the newly created application, go to Add Capabilities - Add by Capability page, and enable both Web Application and Bot capabilities.
drawing
2). Go to Web Application page, configure both Desktop Homepage and Mobile Homepage with the Web Configuration URL from the integration details.
drawing
(See Feishu/Lark development documentation - Configure Application Homepage URL)
3). Go to Event Callbacks - Callback Configuration page, configure the Message Card Request URL (using the Message Card Request URL from integration details) and add the callback.
drawingdrawing

2. Add Redirect URL to Feishu/Lark Application#

Go to Security Settings page, configure the Redirect URL using the Redirect URL from integration details.
drawing
(See Feishu/Lark development documentation - Configure Redirect URL)

3. Request Application Permissions#

Go to Permission Management page, request im:chat and im:message permissions. These permissions will allow the application to access its group chat information and send messages to groups or individuals.
drawing

IV. Application Publication and Usage#


After completing the above steps, proceed with application publication and usage. The application can be used after administrator approval.
Note: Available Range needs special configuration, recommended for All Employees.
drawing
See Feishu/Lark development documentation - Application Publication and Usage.
Once published, you can access the application via mobile/PC client. First-time access requires login and account association (Feishu/Lark 《-》 Flashduty), subsequent uses will be login-free.
1.
Mobile: Access the web application through Feishu/Lark > Workspace > Search application name > Open application.
2.
PC: Access the web application through Feishu/Lark > Workspace > Search application name > Open application.

V. Common Issues#


1.
Unable to deliver messages to individuals, operation record shows Application Not Associated?
Go to Feishu/Lark > Workspace > Search application name > Open application, complete one login and account association (Feishu/Lark 《-》 Flashduty) for the system to obtain user identity for message pushing
2.
Message card buttons not working or showing errors?
Ensure account association is completed. Go to Feishu/Lark > Workspace > Search application name > Open application, complete one login and account association (Feishu/Lark 《-》 Flashduty). If already logged in, try clicking the top-right menu to switch accounts and re-login to bind the account
Ensure sufficient licenses are purchased. You can check license usage in Console > Billing Center
3.
Empty Feishu/Lark group chat list in escalation rule?
Go to Feishu/Lark, select group chat conversation, add the created Flashduty bot as shown below:
Return to the escalation rule configuration page, refresh and reselect the group chat list
drawingdrawing
4.
Feishu/Lark Custom Application API Limits: Feishu/Lark Documentation
Call Volume Limits:
Feishu/Lark VersionTotal Calls/MonthReset Time
Basic Free Version10,000 calls1st of each month
Other VersionsUnlimited-
Frequency Control Limits:
ScenarioLimit
All APIsMaximum 50 calls/second per application
Message Sending APIMaximum 1000 calls/minute per application
Group Bot WebhookMaximum 100 calls/minute
Sending messages to the same user or groupMaximum 5 calls/second
Note: Messages cannot be pushed normally when exceeding limits, please use notification channels reasonably
修改于 2024-11-25 03:16:40
上一页
Jira Issue Events
下一页
Dingtalk Integration
Built with