Connect Feishu to Elisi Agent

Connect a Feishu bot to Elisi Agent

After setup, you can chat with your enterprise bot in Feishu to ask Elisi Agent to record and look up tasks, lists, and other items.

Before you begin

You need:

An Elisi account.
Permission to create and publish a Feishu custom app.
Approval from your enterprise administrator for app permissions, if required.

1. Create a Feishu app

Open the Feishu Open Platform and go to the developer console.
Create a Custom App.
Under Add App Capabilities, enable Bot.
Under Permissions, add:
- Read one-to-one messages sent to the bot.
- Send messages as the app.
- To use the bot in group chats, also add permission to receive messages that mention the bot.

Save the app's App ID and App Secret.

2. Connect the bot in Elisi

Open Settings in Elisi.
Under Elisi AI, select Feishu / Lark Bot.
Select Feishu as the platform. Choose Lark if you use the international Lark service.
Enter an optional bot name, the App ID, the App Secret, and the Verification Token shown in the Feishu console.
Select Connect bot.

After verification, Elisi displays:

An event callback URL.
A one-time account-binding command.

The App Secret is shown only once. Elisi stores it encrypted and does not send it to the Agent.

3. Configure event callbacks

Return to the Feishu Open Platform:

Open Events and Callbacks or Event Subscriptions.
Select Send events to a developer server.
Copy the Event Callback URL from Elisi and paste it as the request URL.
Leave Encrypt Key blank.
Save the URL and wait for Feishu to confirm verification.

Select Add Event and add:

Receive messages (im.message.receive_v1)

URL verification alone is not enough. You must also add im.message.receive_v1.

4. Publish and install the app

Create a new version in the Feishu Open Platform.
Confirm it includes the permissions and message event you just added.
Submit it for review and publish it. Complete administrator approval first if required.
Install the app in your enterprise and ensure your Feishu account is included in its availability scope.

Republish the app after changing permissions or event subscriptions; otherwise, the changes will not take effect.

5. Link your Elisi account

App configuration and publishing often take more than 15 minutes. After publishing, return to Elisi:

Select Generate new binding code on the bot card.
Copy the complete one-time command, for example:
```
/elisi-bind AbCdEf123
```
Within 15 minutes, open a one-to-one chat with the bot and send the command.
After the success message appears, return to Elisi and refresh the status.

Setup is complete when the status changes from Waiting for binding to Connected. The first binding must be done in a one-to-one chat, not a group chat.

6. Use the bot

One-to-one chat: Send text directly to the bot.
Group chat: A linked user must mention the bot in the message.
Disconnect: Select Disconnect on the bot card in Elisi.

The current version supports text messages. It does not support encrypted callbacks using an Encrypt Key, attachments, interactive cards, or sharing one Elisi account among multiple people.

Troubleshooting

Problem	What to check
Callback URL verification fails or returns no challenge	Check the full URL and matching `Verification Token`. Clear the `Encrypt Key` and save again.
URL verification succeeds, but the bot does not respond in a one-to-one chat	Confirm `im.message.receive_v1` is added. Republish, approve, and install the latest app version after adding events and permissions.
Elisi remains at “Waiting for binding”	Generate a new binding code and send the complete command in a one-to-one chat within 15 minutes. Older codes expire.
The account is linked, but the bot does not reply	Check that permission to send messages as the app has been approved and is included in the latest published version.
The bot does not respond in a group chat	Complete the one-to-one binding first, then have the linked user mention the bot in the group.
The bot cannot be found or messaged	Check that the app is installed and your account is in its availability scope.

If the issue continues, check Event Push Records in the Feishu Open Platform for im.message.receive_v1. If there is no record, the event, permissions, published version, or app availability may not yet be active.