YingClaw + Feishu Integration Guide: Bring Your Digital Employee into the Team Chat

Most Chinese enterprises have already made Feishu (Lark) the single entry point for daily work — approvals, docs, meetings, chat all live there. For YingClaw — the digital employee built by the YingClaw.ai team — to truly enter team workflows, it cannot remain a standalone AI running on someone's laptop. It has to be @-mentioned, talked to, and triggered inside Feishu. This is a complete three-step integration guide, plus five real Feishu-side scenarios for your digital employee.

The whole integration requires no code, no public IP, and no prior knowledge of the Feishu open platform API — typing is enough.

Why Your Digital Employee Should Live Inside Feishu

Running YingClaw locally solves a lot, but three core pain points remain:

• Reach is expensive: users have to remember to open YingClaw, which means high forgettability and high collaboration cost.
• Result delivery is awkward: once a task is done, the result can only land in local notifications or a personal WeChat account, with no easy way to share with the team.
• Trigger entry points are scattered: cron jobs, event triggers, and anomaly alerts all need a separate config UI.

Once wired into Feishu, all three pain points disappear — all interactions happen in Feishu. YingClaw can be @-mentioned by anyone in a group, can be talked to directly, and can push scheduled reports, reconciliation results, or anomaly alerts to specified groups or users. The cost of reach drops to zero.

Going further: Feishu itself ships with approvals, docs, Bitable (multi-dim table), meetings, and AI assistant. Once YingClaw is in Feishu, the combination becomes a digital employee that does real work + Feishu's full collaboration suite.

Preparation: Feishu Open Platform Account and Permissions

Before you start, gather four things:

Item	Notes	Time Required
Feishu enterprise admin account	Needed to create the bot	0 minutes if you have one
YingClaw running	On your server or laptop	0 minutes if it's already up
Writable YingClaw working directory	For storing the Feishu credentials	1 minute
Feishu self-built app permissions	Receive messages, send messages, read directory	5–10 minutes

A regular employee account can do most of the setup, but an admin account is recommended to avoid approval workflows slowing things down.

Three Steps to Complete the YingClaw + Feishu Integration

Step 1: Create a Bot App in the Feishu Open Platform

1. Open the Feishu open platform at open.feishu.cn and sign in with your enterprise admin account.
2. Go to Developer Console → Create Self-Built App.
3. Name the app YingClaw Digital Employee, and for the description put YingClaw.ai digital employee, can run scheduled tasks, file operations, and automated workflows.
4. Once created, go to Permissions and enable three baseline scopes:
   • im:message — receive and send messages
   • im:message.group_at_msg — receive group @-mentions
   • contact:user.id:readonly — read user IDs
5. Go to Event Subscriptions and leave the callback URL blank for now (YingClaw will generate it in the next step).

Step 2: Configure Feishu Credentials in YingClaw

This is where YingClaw's experience shines. No documentation diving, no API research — just type this in the YingClaw chat:

"I want to wire Feishu in. Walk me through the setup."

YingClaw will launch an interactive configuration wizard:

1. Ask for the App ID and App Secret of your Feishu app (found in the open platform's Credentials page).
2. Ask you to choose a deployment mode: local, server, or container.
3. Auto-generate an encrypted callback URL — copy that URL back into the open platform's Event Subscriptions page.
4. Feishu will send a verification request to YingClaw, which YingClaw handles automatically.
5. Under Bot Capabilities, enable "receive messages" and "message card callback."
6. Create a version, submit for review (internal enterprise apps usually auto-approve), and publish.

The whole process takes about 5–8 minutes, and a non-developer can complete it end to end.

Step 3: Add the Digital Employee to a Feishu Group

1. In the open platform's App Release page, copy the QR code for "Add bot to a group."
2. Add the bot to any Feishu group (including a one-on-one chat).
3. @-mention YingClaw in the group: @YingClaw please list this week's unread emails.
4. YingClaw replies directly in the group with the result, and tags the request as processed by digital employee @username.

The integration is now complete. All subsequent interactions happen inside Feishu.

Five Real Scenarios for Your Feishu-Side Digital Employee

Scenario 1: @-Mention in a Group to Query Data

In a sales group, type:

@YingClaw list all customers with contract value above 50K RMB this week, sorted by amount descending, post the result in this group.

YingClaw reads the local or database contracts table, filters and sorts by the criteria, and posts the result as a Feishu message card in the group.

Scenario 2: Scheduled Task Result Auto-Pushed to Feishu

Configure a YingClaw cron job (daily at 18:00):

"Aggregate today's website traffic data into a daily report and push it to the operations group with @all."

When the time comes, YingClaw pulls the data, generates the report, and pushes it to the Feishu group — the team gets the day's data before they leave the office.

Scenario 3: Anomaly Alerts Pushed to Feishu Proactively

Configure a monitoring task (every 5 minutes):

"Monitor the order system; if no new orders in 5 minutes, @-the-admin and push to the ops group."

YingClaw uses browser automation to log into the order backend, detects the anomaly, and pushes immediately to Feishu — MTTR drops from 30 minutes to 5.

Scenario 4: Feishu Approval + YingClaw Auto-Execution

Once a Feishu approval is passed, send the approval result to YingClaw:

"Approval BF-2026-0801 has passed; auto-provision the employee account and permissions."

YingClaw receives the approval result, calls the AD / LDAP / internal account system, and the whole flow from "approval passed" to "account provisioned" is automated.

Scenario 5: Feishu Bitable + YingClaw Auto-Fill

After operations staff add customer info to a Feishu Bitable, YingClaw reads the table on a schedule and automatically queries the business registry for the company's credit info, then fills it into the appropriate column. Operations no longer copy-paste manually.

Advanced: Turning Feishu into YingClaw's "Command Center"

Once integrated, Feishu stops being just an IM and becomes YingClaw's command center. A few advanced directions worth trying:

1. Feishu Bitable as task scheduler: keep the list of scheduled tasks in Bitable; YingClaw reads and runs them on time — non-technical staff can edit tasks themselves.
2. Feishu approvals as permission gating: hook YingClaw task execution to Feishu approval flows so sensitive operations require approval.
3. Feishu bot for multi-group control: one Feishu app can join multiple groups; YingClaw plays different roles (ops, sales, support) in different groups.
4. Feishu Docs as the knowledge base: keep team docs in Feishu; YingClaw reads and updates key information automatically — retire the manually-maintained wiki.

FAQ and Pitfall Guide

Q1: Does the Feishu integration require exposing YingClaw to the public internet?

No. YingClaw provides a reverse-channel connection — Feishu initiates the callback, and YingClaw receives it and maintains the connection over a long-lived channel. This means even if YingClaw is on an internal network, on a laptop, or behind a NAT without a public IP, the Feishu integration still works.

Q2: Can one Feishu bot connect to multiple YingClaw instances?

Yes. A single Feishu app (bot) can be authorized for use by multiple YingClaw instances. A "group-based" split is recommended — sales group uses instance A, ops group uses instance B — to avoid task crosstalk.

Q3: Is there a rate limit on Feishu bot messages?

Feishu's API has a default rate limit (50 QPS per app). YingClaw already handles throttling and retries internally, so most scenarios won't hit the limit. For very high-frequency pushes (e.g., second-level monitoring alerts), request a higher quota explicitly.

Q4: Is the Feishu integration data-secure?

YingClaw itself is locally deployed — all data processing happens inside the company network, and Feishu is used only as a "message channel." Business data never touches any third-party server.

Q5: How do I debug a failed Feishu integration?

YingClaw provides a "Feishu integration diagnostics" command. Just type "diagnose Feishu integration" in chat, and it automatically checks App ID, App Secret, callback URL, scope, and every other step. 90% of integration issues get located in under a minute.

Closing Thought

Getting YingClaw running is not hard, but getting it into the team's daily workflow is the real challenge. The Feishu integration is the key step that closes that last mile — turning the digital employee from a personal tool into a team asset.

The team behind YingClaw believes that AI should not just chat — it should do real work. When this digital employee is @-mentioned in Feishu groups, talked to, and triggered on schedule, AI actually starts to weave into organizational processes, rather than staying in the demo stage.

After integration, we recommend picking one or two of the five scenarios above to run a small closed loop, then gradually expanding to more groups, more scheduled tasks, and more business systems. Starting small and proving value beats trying to build an "AI middle platform" on day one.

Sources:

1. YingClaw product knowledge base (yingclaw-knowledge.md)
2. Feishu open platform official documentation: open.feishu.cn
3. Field experience: Feishu integration deployment practice in e-commerce, ops, sales, and engineering scenarios