Lark and Feishu in n8n: Community Nodes Compared

n8n has no built-in Lark or Feishu node: n8n’s integrations documentation lists neither. Feishu is the edition of the platform used in China and Lark the international one, and n8n users reach both through community nodes for messages, Base (Bitable) tables, documents, calendars and event triggers. Several of these READMEs are written in Chinese or Vietnamese, so this guide sums them up in English, using the description and README each author publishes on npm and our own download data.

What do you need?

Lark and Feishu community nodes

Our Lark and Feishu hub lists 23 packages that pass our quality rule, with 3,854 npm downloads a week between them. The most downloaded, with the description each author gives on npm (weekly npm downloads as of 28 October 2026):

Versions and dates come from the npm registry.

@vutiendung/n8n-nodes-lark-base

The most installed package, focused on one thing: records in a Lark or Feishu Base. Its README (in Vietnamese) lists list and search with filters, sorting and views, get, create, update and delete, batch versions of these (up to 500 records per batch, run in sequence), Upsert and Batch Upsert on a unique key field, update or delete by unique key, and a duplicate key check. You paste a /base/ URL or an app token and pick the table.

You create an internal app on the Lark or Feishu open platform, grant it bitable:app:readonly to read or bitable:app to write, and enter its App ID and App Secret in the package’s own credential, choosing the platform. Two cautions from the README: the unique key is not a uniqueness constraint in Lark Base, so parallel executions with the same key can still create duplicates, and failed batch writes are not rolled back.

n8n-nodes-feishu-lark

Built on n8n-nodes-feishu-lite (README in Chinese, with an English version on GitHub), it adds a Lark Trigger and a Lark MCP node. It takes two credentials: Lark Tenant Token API with the app’s App ID and App Secret, and Lark OAuth2 API for acting as a user, where the README recommends the offline_access scope so tokens refresh by themselves. Events arrive in two ways:

• WebSocket: the Lark Trigger. The README says this only works with Feishu in China; international Lark can only use webhooks.
• Webhook: the node’s parse webhook operation together with n8n’s own Webhook and Respond to Webhook nodes; the repository has a demo workflow.

It also has Send and Wait, which sends a message and pauses the workflow until someone answers, and Send Streaming Message for streamed AI agent replies.

n8n-nodes-lark-global

A version of n8n-nodes-feishu-lark for international Lark, with Feishu removed: both credentials point at https://open.larksuite.com. Its English README lists Bitable, Documents, Calendar, Space, Contacts, Messages and Wiki, webhook and WebSocket triggers, and MCP support so AI agents can call Lark’s APIs. It notes that a bot supports only one live WebSocket connection. Its last release dates from October 2025.

@luka-cat-mimi/n8n-nodes-feishu and n8n-nodes-feishu-lite

@luka-cat-mimi/n8n-nodes-feishu is also built on n8n-nodes-feishu-lite. Its Chinese README lists over 140 operations across Wiki, group chats, contacts, tasks, documents, Base (34 operations, with field mapping and upsert), messages, calendar, Aily and Drive, a WebSocket Feishu Trigger, a Feishu Webhook Trigger and a response node for card interactions, plus automatic pagination. It notes that a Feishu app can run only one trigger at a time. n8n-nodes-feishu-lite, the package both build on, covers Wiki, contacts, tasks, spreadsheets, Drive, messages, documents, calendar and Base.

Check each node page here for the latest release and, where it has one, its GitHub repository for open issues before you build on a package.

How to choose

• Syncing data into a Lark or Feishu Base: @vutiendung/n8n-nodes-lark-base, the most used package, with upsert by key.
• Bots and events on Feishu in China: n8n-nodes-feishu-lark or @luka-cat-mimi/n8n-nodes-feishu, both with WebSocket triggers.
• International Lark: n8n-nodes-lark-global, or n8n-nodes-feishu-lark with webhooks.
• An AI agent that works in Lark: the MCP node in n8n-nodes-feishu-lark or n8n-nodes-lark-global.
• An endpoint none of them covers: the HTTP Request node with the open platform’s API documentation.

To install a package on a self-hosted instance, an owner or admin enters its npm name in Settings > Community Nodes; full steps are in How to Install n8n Community Nodes. On n8n Cloud only verified community nodes can be installed, see Verified vs Unverified n8n Community Nodes. Similar guides: Slack and Notion.

FAQ

Does n8n have a Lark or Feishu node?

Not a built-in one. Lark and Feishu support comes from community nodes, or from calling the open platform’s API with the HTTP Request node.

Why doesn’t the Lark Trigger receive events on international Lark?

The n8n-nodes-feishu-lark README says WebSocket events only work with Feishu in China. On international Lark, receive events with a webhook: the node’s parse webhook operation plus n8n’s Webhook and Respond to Webhook nodes.

Can I upsert records into Lark Base from n8n?

Yes, with @vutiendung/n8n-nodes-lark-base, which has Upsert and Batch Upsert on a unique key field. Its README warns that the key is not enforced by Lark Base, so run writes for the same key one at a time.

What is the most used Lark or Feishu community node?

@vutiendung/n8n-nodes-lark-base, with 2,608 weekly npm downloads on 28 October 2026.