Skip to main content

​
Select Platform Domain

When creating a bot, you need to select the Platform Domain in the Adapter Configuration section:
  • Feishu (open.feishu.cn): For mainland China Feishu users (default)
  • Lark (open.larksuite.com): For overseas Lark users
  • Custom: For private deployment users
Select Platform Domain
If you select overseas Lark, make sure to use the open.larksuite.com domain, otherwise the connection may fail. For private deployment users, please select custom and fill in the corresponding domain based on your actual deployment address.
LangBot supports one-click Feishu app creation with automatic credential filling — no manual copy-paste needed.
  1. Open LangBot WebUI, go to Bots > Create Bot
  2. Enter a bot name, select Feishu as the platform/adapter
  3. In the One-Click Create App section that appears, click the Start button
One-Click Create Feishu App
  1. Scan the QR code with Feishu. On your phone, you’ll see the Feishu Open Platform’s bot creation page
  2. Choose to use an existing app or create a new one:
Select on Phone If you choose an existing app, a list of your apps will be shown: Select Existing App
  1. After authorization, the phone will show “Configuration Successful”, and app_id / app_secret will be auto-filled in the LangBot WebUI
Config Success
  1. Manually fill in the bot name — it must match the Feishu bot name, otherwise the bot won’t receive messages in groups
Fill Bot Name
  1. Click Submit to complete

​
Create Bot

Go to the Feishu Open Platform, log in, and create an enterprise self-built application or store application. (difference introduction) alt text alt text Add bot capability to the application: alt text Add the permissions shown in the image in the permission management: alt text If card streaming permissions are required, additionally add the following card creation and update permissions as shown in the image: img_1.png
If you need to change the default card template, you need to modify the card template in the platform adapter’s code yourself.

​
Connect to LangBot

Find app_id and app_secret on the Credentials and Basic Information page. alt text Open LangBot’s Webui configuration page, create a new bot Fill in the relevant information in the form alt text Streaming related: Streaming related After filling in, start LangBot. If configured successfully, the log will show [01-29 23:42:56.796] manager.py (68) - [INFO] : Initializing platform adapter 1: lark, keep LangBot running.
By default, WebSocket long connection mode is used, corresponding to the long connection subscription below. But in some cases (such as international version of Feishu), long connection mode is not available, in which case you need to use Webhook mode, corresponding to the Send events to developer server mode, please refer to the following configuration:
  • enable-webhook: Set to true
  • encrypt-key: Set to Encrypt Key in the Encryption Strategy of the Events and Callbacks page
Note that in Webhook mode, LangBot needs to be deployed on a server with a public IP, and ensure that the firewall has opened the port configured above.
No public server? LangBot Cloud includes built-in domain and HTTPS — get Lark bots working out of the box.

​
Configure Event Subscription

Go to the Events and Callbacks page, configure the subscription method as Long Connection: alt text And add the event: Receive Messages alt text Set up Callback Configuration, select the long connection callback (use webhook if using webhook mode) Set up callback configuration Add the callback Card Callback Interaction Add callback
Webhook mode configuration method:alt textPlease start LangBot first, fill in the Webhook address obtained from LangBot here.

​
Publish Bot

Click Create Version at the top, fill in the version number and other information, click Save below. alt text Add the bot to a Feishu group to use it: alt text alt text Private chat can also be used directly alt text

​
Common Issues

  • Store app bots cannot respond to chat messages immediately after creation/saving. Due to the app_ticket event delay mechanism, you need to wait about 2 minutes before it can work normally.