Overview
RecordEngine can receive documents directly from a Lark (international) or Feishu (China domestic) group chat. When a user drops a PDF or image into the designated intake group, RecordEngine automatically downloads it, runs AI extraction, and files it under the configured contact and folder — no manual upload required.
| Detail |
|---|
| Supported file types | PDF, images (JPG, PNG, etc.) |
| Platforms | Lark (open.larksuite.com) and Feishu (open.feishu.cn) |
| Trigger | File or image message sent to the intake group |
| Processing | Auto-profile detection → AI extraction → outbound webhook |
| Configuration | Settings → General → 🐦 Lark / Feishu Integration |
Prerequisites
- A RecordEngine instance with a public HTTPS URL
- Server URL configured in Settings → General → 🔗 Server URL
- A Lark or Feishu developer account at open.larksuite.com or open.feishu.cn
- At least one Contact and Folder already created in RecordEngine
How It Works
User drops file in Lark/Feishu group
↓
Lark/Feishu POSTs event to RecordEngine
↓
RecordEngine responds 200 OK immediately
↓ (background)
RecordEngine downloads file from Lark/Feishu API
↓
File saved + document record created in RecordEngine
↓
xr-watcher picks up → auto-profile detection → AI extraction
↓
Outbound webhook fires → Make.com → Google Sheets / notifications
Step 1 — Create a Lark / Feishu App
- Go to your developer console:
- Click Create App → Custom App
- Give it a name (e.g.
RecordEngine Intake) and save
- Go to Credentials & Basic Info and note your:
- App ID — looks like
cli_xxxxxxxxxxxxxxxx
- App Secret
Step 2 — Grant App Permissions
In your app’s developer console, go to Permissions & Scopes and enable:
| Permission | Purpose |
|---|
im:message | Read messages sent to the app |
im:message.receive_v1 | Receive message events |
im:resource | Download file and image attachments |
- In your developer console, go to Events & Callbacks → Event Configuration
- Enable events and set the Request URL to:
https://yourinstance.recordengine.ai/api/lark/webhook
Your exact webhook URL is shown in RecordEngine under Settings → General → 🐦 Lark / Feishu Integration → Webhook URL. Copy it directly from there.
- Subscribe to the event:
im.message.receive_v1
- Save. Lark/Feishu will send a challenge request to verify your URL — RecordEngine handles this automatically.
In RecordEngine, go to Settings → General and scroll to 🐦 Lark / Feishu Integration.
| Field | Description |
|---|
| Platform | Select Lark (International) or Feishu (China) |
| App ID | Paste your App ID from Step 1 |
| App Secret | Paste your App Secret from Step 1 |
| Intake Contact | Documents will be filed under this contact |
| Intake Folder | Documents will be placed in this folder |
| Intake Profile | AI extraction profile applied to incoming documents |
| Webhook URL | Read-only — copy this into your developer console |
Choose a dedicated contact and folder for Lark intake (e.g. a contact named “Lark Intake” with a folder named “Inbox”). This keeps incoming documents organised and easy to review before filing them elsewhere.
Step 5 — Add RecordEngine Bot to Your Intake Group
- In Lark/Feishu, open the group you want to use as the intake channel
- Go to group Settings → Bots → Add Bot
- Search for your app name (e.g.
RecordEngine Intake) and add it
From this point on, any file or image sent to this group will be picked up by RecordEngine. Text messages are silently ignored.
Step 6 — Publish Your App
In the developer console, go to App Release → Version Management and publish your app. RecordEngine will not receive events until the app is in Published status.
Testing the Integration
- Send a PDF or image to your intake group in Lark/Feishu
- Within a few seconds, the document should appear in RecordEngine under the configured contact and folder with status Processing
- Once AI extraction completes, status changes to Ready (or Needs Review depending on confidence score)
If you have an outbound webhook configured, a notification will also be sent to your downstream system (e.g. Google Sheets, Lark Base).
Lark vs Feishu
Lark and Feishu are the same platform — Lark is the international version, Feishu is the China domestic version. The only difference is the API base URL:
| Platform | API Base URL |
|---|
| Lark (International) | https://open.larksuite.com |
| Feishu (China) | https://open.feishu.cn |
Supported Message Types
| Message type | Handled |
|---|
| File (PDF, Word, Excel, etc.) | ✅ Yes |
| Image (JPG, PNG, etc.) | ✅ Yes |
| Text message | ⏭️ Ignored |
| Audio / Video | ⏭️ Ignored |
Troubleshooting
Document not appearing in RecordEngine after sending a file
- Confirm your app is Published (not in Draft) in the developer console
- Confirm the Request URL in Events & Callbacks matches your RecordEngine webhook URL exactly, including
https://
- Confirm App ID and App Secret are saved correctly in RecordEngine Settings
- Check that the RecordEngine bot has been added to the intake group
Webhook URL verification failed in Lark/Feishu developer console
- Confirm your RecordEngine instance is publicly accessible over HTTPS
- Confirm the Server URL is set in Settings → General → 🔗 Server URL
- The challenge verification is handled automatically — no additional configuration is needed
Documents arriving twice
- Check whether any Make.com scenario is also forwarding Lark events to RecordEngine. If so, deactivate it — RecordEngine handles the full intake flow internally without Make.com involvement.
File downloaded but extraction profile is wrong
- Go to Settings → General → 🐦 Lark / Feishu Integration and update the Intake Profile
- For mixed document types, consider using the Universal Invoices and Receipts profile, or enable auto-profile detection
