Feishu Binding
- 1.3k installs
- 21 repo stars
- Updated August 3, 2026
- starchild-ai-agent/official-skills
feishu-binding is an agent skill that binds Feishu accounts and webhooks for starchild agent notifications and workflow triggers.
About
The feishu-binding skill configures Feishu account linking and webhook endpoints for starchild-ai-agent official workflows. It documents OAuth or token setup steps, required app permissions, channel binding verification, and test message flows so agents can send notifications or receive trigger events from Feishu. Agents validate that secrets are stored safely, scopes match intended bot capabilities, and binding status is confirmed before enabling production automations. Use when integrating Feishu messaging with starchild agent pipelines for alerts, approvals, or human-in-the-loop steps.
- Feishu account binding and webhook setup for starchild agents.
- Documents permissions, OAuth or token steps, and verification flows.
- Supports notification and trigger integrations in agent pipelines.
- Validates secret handling and scope requirements before production.
- Enables human-in-the-loop approvals via Feishu messaging.
Feishu Binding by the numbers
- 1,300 all-time installs (skills.sh)
- +55 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #238 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
feishu-binding capabilities & compatibility
- Capabilities
- oauth or token binding setup · webhook endpoint configuration · permission scope validation · test notification flows · human in the loop messaging hooks
- Use cases
- orchestration · email
What feishu-binding says it does
feishu-binding
npx skills add https://github.com/starchild-ai-agent/official-skills --skill feishu-bindingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.3k |
|---|---|
| repo stars | ★ 21 |
| Last updated | August 3, 2026 |
| Repository | starchild-ai-agent/official-skills ↗ |
How do I connect Feishu messaging to starchild agent workflows with proper auth and webhooks?
Bind Feishu accounts and webhooks for starchild agent notifications and workflow triggers.
Who is it for?
Teams integrating Feishu alerts or approvals into starchild official agent automations.
Skip if: Skip for Slack or Teams integrations outside Feishu binding scope.
When should I use this skill?
User sets up Feishu binding, webhooks, or bot notifications for starchild agents.
What you get
Verified Feishu binding with tested notifications or triggers and documented permission scopes.
- Feishu/Lark authorized connection
- Binding status verification
- Disconnected channel state
By the numbers
- Skill version 1.0.0
- Tags: feishu, lark, binding, connection, device-flow
Files
📱 Feishu/Lark Binding
Connect / disconnect the user's Feishu (飞书) or Lark account so the agent can chat via the Feishu/Lark app.
The feishu tool stays built-in. This SKILL.md is the reference doc.
See also
config/context/references/messaging-channels.md— how messages are routed across channelsskills/wechat-binding/SKILL.md— analogous WeChat flowskills/tg-bot-binding/SKILL.md— analogous Telegram flow
---
Brand selection
| Brand | Region | Domain |
|---|---|---|
feishu | China mainland (中国大陆) | feishu.cn / accounts.feishu.cn |
lark | International | larksuite.com / accounts.larksuite.com |
Ask the user which brand they use. Default to feishu if unclear. Chinese-speaking users almost always use feishu.
---
Typical binding flow
connect(brand) → user scans QR / opens link → poll(device_code) → done1. Start device flow: feishu(action="connect", brand="feishu") — returns verification_uri, device_code, and a QR code image saved to workspace. 2. Show BOTH options to the user:
- QR code scan: Display the QR code image inline using the
markdown_imagefrom the result (e.g.). The user scans it with their Feishu/Lark app. - Direct link: Show the
verification_urlas a clickable link. The user opens it in their browser, logs in to Feishu/Lark, and confirms.
3. Wait for the user to confirm. Don't auto-poll — let them say "done" / "confirmed" / "已确认" / "scanned" first. 4. Poll for completion: feishu(action="poll", device_code=<from step 1>, brand=<same brand>).
status: "done"→ binding complete, congratulate the user.status: "pending"→ ask the user if they've scanned the QR code or opened the link and confirmed.status: "expired"→ the device flow expired (typically 5 minutes). Start over withconnect.
5. Confirm to user: "Feishu/Lark connected! You can now chat with your agent on Feishu/Lark."
---
Actions
| action | required params | purpose |
|---|---|---|
status | — | Current Feishu/Lark app state. Use to check if already connected. |
connect | brand (optional, default "feishu") | Start device flow. Returns verification URL + device_code. |
poll | device_code, brand | Check if user has confirmed authorization. Returns status. |
disconnect | — | Unbind Feishu/Lark app (destructive — confirm with user first). |
---
Channel-aware QR / link display
| User channel | How to show |
|---|---|
| Web | Include file_path (QR image) in your reply — frontend renders it inline. Also show the link. |
| Telegram | send_to_telegram(file_path=<qr_path>, message_type="photo") + include the link in the caption |
| Show the link only (user can't scan a QR inside WeChat for Feishu) | |
| Feishu | (User is already on Feishu — they don't need to bind. Tell them it's already connected or check status.) |
---
Key differences from WeChat / Telegram
| Aspect | Feishu/Lark | Telegram | |
|---|---|---|---|
| Auth method | Device flow (URL) | QR code scan | Bot token |
| User action | Open URL + confirm in app | Scan QR + confirm | Create bot via @BotFather |
| Credential | None (device flow handles it) | bot_token (from QR) | bot_token (from BotFather) |
| Brand choice | feishu / lark | N/A | N/A |
---
Critical rules
- Don't auto-poll after
connect. Wait for user confirmation that they've opened the link and confirmed in Feishu/Lark. Auto-polling wastes API calls. - Device flow expires in ~5 minutes. If
pollreturnsexpired, tell the user and start a newconnect. - `disconnect` is destructive — confirm with the user before calling it. It will stop the Feishu/Lark gateway instance.
- Brand matters —
feishuandlarkuse different API domains. Using the wrong brand will fail silently or redirect to the wrong login page. - One app per user — a user can only have one Feishu/Lark app at a time. If they want to switch brands, they must
disconnectfirst, thenconnectwith the new brand.
---
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
connect returns error | User already has an active app | Call status first; if active, ask if they want to disconnect and rebind |
poll returns expired | User took too long to confirm | Start a new connect |
poll returns pending repeatedly | User hasn't opened the URL yet | Remind them to open the verification URL |
| User says "I can't find the link" | URL was in a previous message | Re-run connect to get a fresh URL |
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.591k39.6k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.494kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.493kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.492kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.492k
Twitter AutomationAutomate X/Twitter posts, scheduling, and engagement via X API integration441k669How it compares
Use for Feishu/Lark device-flow channel setup; use tg-bot-binding or wechat-binding skills for Telegram or WeChat agent routing instead.
FAQ
What does feishu-binding configure?
Account linking, webhook endpoints, permissions, and test notification flows for Feishu.
Does it handle secrets safely?
It validates secure secret storage and required app scopes before enabling production use.
What workflows use Feishu binding?
Agent notifications, triggers, and human-in-the-loop approval steps in starchild pipelines.