🇨🇳 Chinese Platforms

Lark Integrationv1.0.0

Name: Lark Integration
Author: boyangwang

lark-integration

Connect Lark (Feishu) messaging to OpenClaw via webhook bridge. Supports text, rich text (post), and image messages bidirectionally. Use when setting up Lark/Feishu as a messaging channel, receiving messages with images, sending replies back to Lark, reading Lark documents/wikis/bitables, or troubleshooting Lark integration issues. Covers both Lark International (larksuite.com) and China Feishu (feishu.cn).

latest

Download Package View on ClawHub

Installs (all time)

Installs (current)

Downloads

3.6K

Stars

CreatedFeb 1, 2026

UpdatedApr 16, 2026

Install & Quick Start

Install via ClawdBot CLI:

clawdbot install boyangwang/lark-integration

Skill Package4 files

📋SKILL.mdmarkdown

Failed to load file.

Quality Score

A71/100

Grade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.

Market Validation18/35

· 13 installs (average)
· 3618 downloads (high demand)
· 2 stars

Documentation20/25

· SKILL.md present
· Detailed documentation (≥3000 chars)
· Contains usage examples or trigger description
· Detailed summary

Package Completeness8/15

Security Analysis

💙 Low Risk

UNKNOWN_DATA_SINKhigh

Sends data to undocumented external endpoint (potential exfiltration)

webhook → http://YOUR_IP:3000/health`

UNDOCUMENTED_EXTERNALlow

Calls external URL not in known-safe list

https://open.larksuite.com

KNOWN_EXTERNALlow

Uses known external API (expected, informational)

open.feishu.cn

AI Analysis

The skill's external API calls (larksuite.com, feishu.cn) are consistent with its stated purpose of Lark/Feishu integration. The 'UNKNOWN_DATA_SINK' signal for a /health endpoint is likely an internal monitoring endpoint for the bridge server, not a data exfiltration risk. No credential harvesting, hidden instructions, or obfuscation is present.

💡

Usage Guide

Generated Mar 1, 2026

IT administratorsCustomer support managersintermediate

💡 Application Scenarios

Customer Support AutomationE-commerce

Automate responses to customer inquiries in Lark group chats, handling text and image queries. The bot can be triggered by mentions or questions, reducing manual support workload and providing 24/7 assistance.

Internal IT HelpdeskTechnology

Set up a Lark bot to troubleshoot common IT issues, such as password resets or software errors, by analyzing text and screenshot attachments. It routes complex cases to human agents based on trigger words.

Document Management AssistantConsulting

Enable employees to fetch and summarize Lark documents, wikis, or spreadsheets via chat commands. This streamlines access to company knowledge bases without leaving the messaging interface.

Sales Team CoordinationSales

Use the bridge to send automated updates from CRM systems into Lark sales channels, with rich text posts. The bot can also collect feedback or questions from team chats for follow-up.

Educational Content DeliveryEducation

Deliver course materials and assignments through Lark, allowing students to submit images or ask questions. The bot responds with tailored resources or escalates to instructors based on query complexity.

💼 Business Models

SaaS SubscriptionRecurring subscription fees

Offer the Lark integration as part of a subscription service for businesses, providing ongoing support, updates, and premium features like advanced document parsing. Revenue comes from monthly or annual fees per user or tenant.

Consulting and SetupProject-based fees

Provide one-time consulting services to help companies configure the bridge, set up Lark apps, and train teams. This model targets organizations needing custom integration or troubleshooting assistance.

Freemium with Add-onsUpsell from free tier

Offer a basic version of the skill for free, with paid add-ons for features like high-volume messaging, priority support, or integration with other enterprise systems. This attracts small teams and scales with usage.

💬 Integration Tip

Ensure the Lark app has all required permissions, like im:message and im:resource, and test the webhook connectivity before deployment to avoid common errors.