Resources · Zapier integration

Lark Zapier integrationAutomate Lark with Zapier.

Lark Zapier integration: 2 triggers (both instant), 14 actions and 10 searches. A Zap can react to what happens in a Lark group chat, then write into Base, Docs, Sheets, Calendar or Tasks. Here is what each step does, what it costs and where it breaks.

See the 26 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Lark Zapier integration actually does for you

The Lark Zapier integration links your Lark workspace to the other apps you run, without code. Something happens in a Lark group chat, or in another tool, and Zapier writes the follow-up for you in Lark: a message, a task, a record, a document or a calendar event.

Three results come up again and again. First, a request log: Receive Message in Lark Group Chat feeds Create New Base Table Record, so every request posted in a support chat lands as a row in a Lark Base. Second, team alerts: a form or a CRM in another app fires the Zap, and Send Message to Lark Group Chat (As Bot) posts the news where the team already reads. Third, onboarding: New User Added to a Group Chat sends a welcome through Send Direct Message (As Bot), then Create New Lark Task books the first to-do.

Now the limits. Both triggers watch group chats only. Nothing starts a Zap when a Base record, a document, a task or a calendar event changes, so those need another app as the starting point. There is no delete action either: the Zap creates and updates, it never removes. And the group message sent as a user takes plain text only.

Weighing other tools for the same job? See our n8n vs Zapier and Make vs Zapier comparisons.

Vocabulary

Zapier words in one minute

Seven words come back on every line of this page. Here they are in plain English, once.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event.
Action
What the Zap does after it starts: the step that writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completes without error; your plan counts those, nothing else.
Instant vs polling
An instant trigger is pushed by the app the moment the event happens. A polling trigger is checked by Zapier on a timer instead.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and quietly stops it otherwise.
Search step
A step that looks up something already in an app, so later steps can reuse what it found, like a chat ID or a task GUID.
Cost

What a Lark Zap really costs

Lark is not a premium app, so it works on the Free plan. Zapier bills tasks, and only finished actions count as tasks.

  • Free plan100 tasks per month, unlimited Zaps
  • Zap size on FreeTwo steps: one trigger, one action
  • Lark triggers2 instant, 0 polling
  • Premium appNo

The trigger never costs a task. Each successful action counts on its own, so a three-action Zap eats three times what a one-action Zap does, while a failed action costs nothing at all. The Free plan builds two-step Zaps only: add a filter, a search or a second action and the Zap needs a paid plan. The interval grid below applies to polling triggers only, and both Lark triggers are instant, so it never slows them down.

Connect

Connect your Lark account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Lark account linked to Zapier once, then reused by every step that touches Lark.

  2. 02

    Pick Lark in the dialog

    Type Lark in the search box of the dialog, select it, then click Add connection. A new browser tab opens on the Lark sign-in screen. Use the account that sits in the chats and folders you want to automate.

  3. 03

    Sign in and grant access

    Log in to Lark in that tab and allow Zapier to reach the account. Beyond your own items, the Zap can only touch chats, Bases and folders where this account already has read or write access.

First Zap

Your first Zap: log support requests in a Lark Base

GoalEvery message posted in a support group chat that meets your condition becomes a new row in your request-tracking Base.

  1. 01

    Create the Zap

    Click to create a new Zap. You build it top to bottom: the app and event that start it, then the apps and actions that follow, with the fields mapped between steps.

  2. 02

    Set the trigger

    Pick Lark, then Receive Message in Lark Group Chat. Choose the support group in the Channel ID box, after adding the Zapier bot to that chat.

  3. 03

    Test it on a real message

    Post something in the chat, then run the test. Zapier brings back the three most recent items from your account, so you map fields on a real message.

  4. 04

    Add the filter

    Click the plus icon, add Filter and set the text rule on the message content. This makes the Zap multi-step, so it needs a paid plan.

  5. 05

    Add the Base action

    Choose Create New Base Table Record. Paste the app token from the Base URL, pick the table, then map the message content into the columns.

  6. 06

    Test and publish

    Run each step once and read what comes back. When the row shows up in the Base, click Publish to switch the Zap on for every new message.

Triggers

Lark triggers: what starts a Zap

2 events start a Zap when something happens in Lark, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Receive Message in Lark Group Chat

Instant trigger

In Zapier“Triggers when a new message is received in a Lark group chat (Bot and user have to be in the group already)”

Each new message posted in the group chat you choose starts the Zap and hands over its text, so the rest of the Zap can log it, route it or answer it somewhere else.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a shared requests channel where every message should become a row, a task or an alert in another tool.
Watch out
the bot and your user must already be members of the group, or the chat never appears in the Channel ID list. If a later step posts back into the same chat, that post can fire the Zap again.
2

New User Added to a Group Chat

Instant trigger

In Zapier“Triggers when a new user is added to a group chat (Bot has to be in the group already)”

Fires when someone is added to a group chat you picked, which makes it the natural starting point for welcome flows and access checklists.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a new hire joins the team chat, and you want a direct welcome note plus a first onboarding task without anyone remembering to send them.
Watch out
the Zapier bot has to be in that group before the event happens. People added before you published the Zap are not picked up later.
Actions

Lark actions: what the Zap writes

Lark gives you 14 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create New Base Table Record

Action

In Zapier“Creates a new record in a Base table”

Adds a fresh row to a table inside a Lark Base, filled with whatever the earlier steps carried.

When to use it
turning form answers or chat requests into a shared tracking table.
Watch out
the app token is read from the Base URL, so open the Base in your browser and copy that part before you set the step.
2

Update Base Table Record

Action

In Zapier“Updates an existing record in given Base table”

Rewrites the columns of a row that already exists in a Base table, for example a status or an owner.

When to use it
a deal changes stage in your CRM and the matching Base row should follow.
Watch out
it needs the record ID on top of the app token and table ID, so keep that ID from the step that created the row.
3

Create New Lark Document

Action

In Zapier“Creates a new Lark Document”

Opens a new Lark document with the name you give it, saved inside the folder you choose.

When to use it
a meeting is booked elsewhere and you want an empty notes document waiting in the team folder.
Watch out
the folder picker only fetches the first 5000 folders of your drive, so a very large drive may hide the one you want.
4

Create New Lark Folder

Action

In Zapier“Creates a new, empty Lark folder”

Builds an empty folder inside a parent folder of your Lark drive, named from data the Zap received.

When to use it
one folder per new client or project, created the moment the deal is signed.
Watch out
the parent folder is chosen from the same list capped at the first 5000 folders, searchable by keyword.
5

Create Lark Sheet

Action

In Zapier“Create a new Sheet in Lark”

Creates a new spreadsheet in Lark, placed in the folder you designate by name and token.

When to use it
a fresh budget sheet for every new project, ready before the kickoff.
Watch out
both the folder name and the folder token are required, so have the target folder ready before you build the step.
6

Create New Lark Task

Action

In Zapier“Crreates a new task in Lark”

Puts a task on someone's Lark list, with a summary, a description, an assignee and a due date.

When to use it
a request arrives by email or chat and should land as a to-do for the right person.
Watch out
the due date expects Unix time in milliseconds, not a readable date, so a formatting step may be needed first.
7

Invite User to Lark Group Chat

Action

In Zapier“Invites a user to a Lark Group Chat”

Adds a person to an existing group chat, given the chat ID and that person's user ID.

When to use it
a new hire record in your HR tool should put them straight into the team channel.
Watch out
you need both IDs; the searches Search Group Chat in Lark and Search Users in Lark can find them first.
8

Create New Lark Calendar Event

Action

In Zapier“Creates a new Lark Calendar event”

Places an event on a Lark calendar, with a summary, a description, a start and an end.

When to use it
a booking taken in another tool should block time on the team calendar.
Watch out
start and end are timestamps counted in seconds, not readable dates, so convert them before this step.
9

Send Direct Message (As Bot)

Action

In Zapier“Sends a direct message to a specified user as a Bot”

Delivers a private message to one person, signed by the bot rather than by you.

When to use it
automatic reminders or alerts that should clearly come from a system, not a colleague.
Watch out
the step asks for the receiver ID, so look it up with a user search when you only have a name or email.
10

Send Direct Message (As User)

Action

In Zapier“Send a direct message to another user using the sending user's identity”

Sends a private message under your own identity, so the receiver sees it as coming from you.

When to use it
a personal follow-up after a form submission, where a bot name would feel cold.
Watch out
every message goes out in your name, so keep the wording something you would actually sign.
11

Send Message to Lark Group Chat (As Bot)

Action

In Zapier“Sends a message to a Lark Group Chat as a Bot (Bot has to be in the group already)”

Posts into a group chat under the bot's name, which is the cleanest way to push alerts to a whole team.

When to use it
new orders, failed payments or form leads announced where everyone already reads.
Watch out
the "Full Zapier Experience" bot has to be added to the group, or the post fails.
12

Send Message to Lark Group Chat (As User)

Action

In Zapier“Sends Message To A Lark Group Chat Using The Sending User's Identity”

Writes into a group chat as you, not as the bot, so the message reads like a normal post.

When to use it
a project recap you want to appear under your name in the team channel.
Watch out
plain text only, both you and the bot must be in the group, and only the first 100 group chats are listed.
13

Update Lark Calendar Event

Action

In Zapier“Updates an existing Lark Calendar event”

Changes an event already on a Lark calendar, such as its time or description.

When to use it
a client moves a meeting in your booking tool and the Lark event should move too.
Watch out
it needs the calendar ID and the event ID; Search Lark Calendar Event can fetch the second one.
14

Update Existing Lark Task

Action

In Zapier“Updates an existing task in Lark”

Edits a task that already exists in Lark, found by its GUID, its unique identifier.

When to use it
a ticket changes in your helpdesk and the matching Lark task should reflect it.
Watch out
summary, description and due date are required each time, so map them again even when unchanged.
Searches

Lark searches: finding what already exists

10 search steps look for data that already exists in Lark, so a later step can use it.

A search step looks something up in Lark and hands it to the next steps. In the editor, Lark searches sit at the bottom of the Action event list, under SEARCH. Each one adds a step, which makes the Zap multi-step and needs a paid plan.

1

Search Lark Base

Search

In Zapier“Search for a Lark Base by name or keyword”

Looks for a Lark Base from a keyword in its name, so a later step knows which Base to write into.

When to use it
one Base per client, picked by the client name the trigger received.
Watch out
the keyword box is required, so map a value that is always filled in, or the step has nothing to look for.
2

Search Lark Docs

Search

In Zapier“Search for a Lark Base by name or keyword”

Finds a Lark document from a keyword, then passes it on to the next step of the Zap.

When to use it
sharing the link of an existing brief in a chat message rather than pasting it by hand.
Watch out
a vague keyword can match several documents, and the multiple-results setting then decides which one moves on.
3

Search Lark Calendar Event

Search

In Zapier“Search user's Lark calendar events”

Scans one calendar for events whose text matches your keyword, and returns the match.

When to use it
just before Update Lark Calendar Event, to get the event ID.
Watch out
the keyword is capped at 200 characters and the calendar ID is required.
4

Search Lark File

Search

In Zapier“Search Lark File by key word”

Hunts for a file stored in Lark from a keyword and returns it for the following steps.

When to use it
a contract signed elsewhere, and the Zap needs the matching file already uploaded to the drive.
Watch out
when no file matches, the Zap stops right here unless you switched on the no-results setting.
5

Search Group Chat in Lark

Search

In Zapier“Searches for a Lark Group Chat that users or bot are in by name”

Looks up a group chat by its name, among the chats that you or the bot belong to.

When to use it
getting the chat ID before Invite User to Lark Group Chat.
Watch out
a chat neither of you is in stays invisible to this search.
6

Search Lark Sheets

Search

In Zapier“Search Lark Sheet by keyword”

Returns a Lark spreadsheet that matches a keyword, ready for the next step to use.

When to use it
linking the right project sheet in a recap message, chosen from the project name.
Watch out
name your project sheets the same way every time, or the keyword will miss the one you expect.
7

Search Lark Slides

Search

In Zapier“Search Lark Slide by keyword”

Locates a Lark presentation from a keyword in its title.

When to use it
sending the latest sales deck to a new lead, found by its name rather than by a fixed link.
Watch out
two decks with close titles both match, so give the current one a title nothing else shares.
8

Search Lark Task by Complete Status

Search

In Zapier“Search Lark Task by Complete Status”

Pulls tasks according to whether they are done or still open.

When to use it
a check that lists open tasks before posting a reminder in the team chat.
Watch out
the completion box is the only criterion, so it does not narrow by person or project.
9

Search Task by GUID

Search

In Zapier“Search User's Task By GUID (get one task through GUID)”

Fetches one precise task through its GUID, the unique ID Lark gives every task.

When to use it
you stored the GUID earlier, in a Base row for instance, and need the task details back.
Watch out
the GUID is required and must be exact, so store it the moment the task gets created.
10

Search Users in Lark

Search

In Zapier“Searches For An User Using Either Their Name Or Email”

Finds a person in Lark from their name or their email address, and returns their user ID.

When to use it
the step before any direct message or invite, when your other tool only knows an email.
Watch out
a common name can match several people, so searching by email is the safer choice.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there. Switch it on and the Zap carries on, empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Lark offers no such variant, so you will not see it on these searches.
  3. If multiple search results are found?
    Several matches: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When a Lark Zap breaks

Zapier attaches no help article to Lark and lists no Lark-specific rate limit. What breaks is mostly general Zapier behavior, plus the bot membership rule.

  • The bot is not in the group

    The triggers and the bot messages assume the Zapier bot already sits in the chat. Without it, the chat is missing from the list or the post fails.

  • The Zap feeds itself

    A Zap that posts back into the chat its trigger watches fires again on its own message, over and over, and burns through your task count fast.

  • Old messages are ignored

    A Zap only reacts to what happens after you switch it on. Earlier messages or members are never picked up; moving that backlog is a separate job.

  • A sudden flood is held back

    When a trigger suddenly returns a huge batch, after a bulk import for instance, Zapier's flood protection can hold the runs back.
Need help

Need help automating Lark with Zapier?

A person reads every message.

FAQ

Lark and Zapier: common questions

01Is the Lark Zapier integration free?
Yes, within the Free plan limits. Lark is not a premium app, so it runs on the Free plan, which gives 100 tasks per month and unlimited Zaps. The catch is size: on Free, a Zap holds one trigger and one action, nothing more. As soon as you add a filter, a search or a second action, the Zap becomes multi-step and needs a paid plan. Many useful Lark flows, like finding a user ID before sending a message, need that search step.
02How many tasks does a Lark Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that logs every group message into a Base uses one task per message. Add a direct message after it and each run costs two. Actions that fail are not counted. Watch the group triggers on busy chats: every single message starts a run, so a chatty channel can use up the 100 monthly tasks of the Free plan sooner than expected.
03Is Lark to Zapier real time?
Yes, both Lark triggers are instant. Lark tells Zapier the moment a message arrives or someone joins a group, and the Zap starts right away, whatever your plan. The interval grid (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) only applies to polling triggers, and Lark has none. The actions run as soon as the trigger hands over the data. If your Zap starts in another app, that app's trigger decides the delay.
04What does connecting Lark to Zapier require?
A Lark account, plus read or write access to the chats, Bases and folders you do not own but want the Zap to touch. The connection itself takes three moves: add the connection from the Apps page, sign in to Lark in the tab that opens, and grant access. For group chats there is one more requirement: the Zapier bot has to be added to each group before the triggers or bot messages can use it.
05Why is a Lark group chat missing in Zapier?
Because the Zapier bot, and sometimes you, are not in that group yet. The triggers and the bot messages need the bot already in the chat. For a message sent as a user, both you and the bot must be members. The picker also lists only the first 100 group chats of the account, searchable by keyword. Add the bot to the group, then reload the list in the editor.
06What if the Lark operation you need is missing?
Start from another app or chain existing steps. Lark offers no trigger on new Base records, documents, tasks or calendar events, and no delete action. A common workaround is to let the event that caused the change, a form or a CRM update, start the Zap, then use a Lark search to find the item and an update action to change it. Beyond that, the job falls outside the steps Zapier offers for Lark.
07Zapier, Make or n8n for Lark?
It depends on three criteria rather than a ranking. Setup speed: Zapier gives 26 ready steps for Lark and a guided editor. Volume: Zapier bills each successful action as a task, so high-traffic chats weigh on the plan. Control: if you need operations Zapier does not offer, such as deletions or a trigger on new Base records, check what the other tools expose for Lark before choosing. Compare the billing model against your expected message volume.
Same platform

Other docs you might need on this stack.

Browse all integrations