Feishu / Lark
Org-level connection
Feishu / Lark is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
Getting your API key
Create a self-built app in your Feishu (open.feishu.cn) or Lark (open.larksuite.com) developer console.
Under Permissions & Scopes, enable the scopes you need (im, contact, docx, sheets, bitable, calendar, approval) and publish an app version for them to take effect.
Copy the app's App ID and App Secret.
Paste them below as "App ID|App Secret" (App ID, a pipe, then App Secret).
Set Region: enter "feishu" for the China platform (open.feishu.cn) or "lark" for international (open.larksuite.com). Defaults to lark.
Ready to connect?
Sign in to On Belay and open the Integrations page to add Feishu / Lark.
Permissions (scopes)
These are the data scopes On Belay can be granted for Feishu / Lark. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
im:read | Read messages and chats | Read only |
im:write | Send messages | Read / Write |
contact:read | Read users and departments | Read only |
docs:read | Read Drive files and documents | Read only |
sheets:read | Read spreadsheets | Read only |
bitable:read | Read Base tables and records | Read only |
bitable:write | Create Base records | Read / Write |
calendar:read | Read calendars and events | Read only |
calendar:write | Create calendar events | Read / Write |
approval:read | Read approval instances | Read only |
approval:write | Create approval instances | Read / Write |
Troubleshooting
"Invalid API key" or "Unauthorized" error
Connected but Claude can't access data
The key expires or stops working
Still stuck? We're happy to help.
Contact support →