Lark Group Bot

Send text, rich posts, images, group share cards, and interactive cards to a Lark group chat through the custom bot webhook. Agents put an alert or an approval card in front of the group that owns it.

5 actions Custom auth available

Lark Group Bot website ↗ Platform Documentation ↗ Capability data verified 2026-08-03

A release pipeline finishes and marks a build ready to announce

Agent collects the version, the services touched, and the regressions still open

Agent confirms the signing secret is configured and the payload is inside the webhook's size limit

Agent notices the draft carries a mention of everyone, which pushes a notification to every member of the group

Agent posts the draft and the group size to the release manager on the channel FlowRunner is listening on

The release manager approves the wording and the mention, and the agent sends the rich post to the group

What This Integration Enables

This connector talks to Lark through the custom bot incoming webhook, and the shape of that webhook decides what the flow can do. It is outbound only. It reaches exactly one group chat, the one the bot was added to, and it exposes no read call and no event stream, which is why there are five send actions and no triggers here. What it gives up in reach it repays in setup cost: a URL copied out of the group's own bot settings, no application registration, no tenant admin involved.

Within those five actions the range is real. Plain text for a one line alert. Rich posts when an update needs a title, structure, links, and mentions. Images for a rendered chart or a screenshot. Group share cards to hand the room an entrance to another chat. Interactive cards built from Lark's card JSON when the message should read like a small dashboard. One honest limit is worth knowing before you design around it: interactive cards from a custom bot support buttons and text links, but callback-based card elements are not delivered back to custom bots. The card can present a decision and point at where to make it. It cannot collect the answer. Any decision the flow waits on comes back through a human-in-the-loop step on a channel FlowRunner can actually read, and the flow resumes from there.

This connector targets the international Lark Suite edition on open.larksuite.com. Teams on the Chinese Feishu edition should use the Feishu Group Robot connector instead, because the two run on separate domains and a webhook issued by one will not authenticate against the other.

Without FlowRunner

Announcements written by hand Someone assembles the version, the changes, and the caveats after the work is already done

Broadcast by habit Every announcement pings the whole group because nobody stopped to ask whether it should

Formatting lost Links and structure get flattened into a paragraph people skim past

With FlowRunner

Assembled by the flow The version, the changes, and the open items are gathered the moment the pipeline finishes

Broadcast on purpose Anything that notifies every member is approved by a person before it fires

Built for the surface Rich posts and cards carry structure and links so the group reads the state, not a paragraph

Use Case Scenarios

Payment and revenue cards into the commercial group

Each time Stripe records a payment above the threshold the team cares about, the agent builds a card with the customer, the amount, the plan, and whether this is new business or a renewal, and posts it into the commercial group. The card format matters here: the group is scanning for a shape, not reading sentences, and a card gives them the same layout every time. Smaller payments are aggregated into one daily rich post instead of firing individually, because a group that gets pinged for everything stops reading the pings.

SLA breach alerts routed to the group that owns the customer

When a Zendesk ticket crosses its SLA, the agent posts an alert into the Lark group of the team that owns that account, with the ticket, the customer, how long it has been open, and the last agent to touch it. Because each Lark group has its own bot webhook, routing by account means selecting the right webhook rather than tagging people inside a shared room. The team that can act sees it, and the teams that cannot are not interrupted.

Weekly operating report as a rich post

A scheduled flow pulls the week's numbers, renders the two charts worth looking at, uploads them through the Lark Open Platform image API, and posts a rich post with the figures, the images, and links back to the underlying dashboards. Send Image Message takes an image key rather than a file, so the upload happens ahead of the send using a Lark app credential. The report lands in the group at the same hour every week, which is the point.

Human-in-Loop Highlight

A rich post that mentions everyone does not just appear in a group. It pushes a notification to every member's phone, wherever they are and whatever hour it is for them, and this connector has no delete action, so there is no version of taking it back. That makes the broadcast, not the content, the thing worth stopping for. When a flow is about to fire a message that notifies the whole group, the agent holds it: "Release 4.2 is ready and the rule says announce it with an at-everyone mention to the product group, which has 380 members. Two regressions are still open against this build. Send with the mention, send without it, or hold until the regressions close?" The release manager answers on the human-in-the-loop channel they already use, and the agent sends exactly the version they picked. The agent is happy to write the announcement. It should not be the one deciding to interrupt 380 people.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

Messages

Send Text Message Sends a plain text message to the group chat the bot was added to. Used for single fact alerts where formatting adds nothing.
Send Rich Post Message Sends a rich text post with an optional title, styled paragraphs, links, and mentions. Used for release notes, weekly reports, and any update the group should be able to click through from. Mentions here reach real people's notifications, so a broadcast belongs behind an approval.
Send Image Message Sends an image to the group by its image key. Keys are produced by the Lark Open Platform image upload API using a Lark app credential, so the upload is a step in the flow ahead of the send.

Cards and Sharing

Share Group Chat Card Sends a share card for another group chat into the group the bot was added to, giving the room a tappable entrance to that chat. Used when the point of the message is to move people, not to inform them.
Send Interactive Card Sends an interactive card built with Lark's card JSON. Used for status summaries and approval requests that need to be read at a glance. Buttons and text links work; callback elements are not delivered to custom bots, so the card links out to the decision surface rather than capturing the answer itself.

Frequently Asked Questions

What can FlowRunner do with Lark Group Bot?

FlowRunner agents can run Send Text Message, Send Rich Post Message, and Send Image Message in Lark Group Bot, plus 2 more actions.

Does connecting Lark Group Bot to FlowRunner require OAuth?

Lark Group Bot uses a custom authentication method to connect to FlowRunner.

Can Lark Group Bot trigger a FlowRunner workflow automatically?

Lark Group Bot doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Lark Group Bot

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us