Feishu Group Robot

Post messages into a Feishu group chat through the custom bot webhook. Agents deliver alerts and approvals to the group that owns the decision, with optional signature verification on every send.

5 actions Custom auth available

Feishu Group Robot website ↗ Platform Documentation ↗ Capability data verified 2026-08-03

A monitoring alert opens a production incident in the ticketing system

Agent pulls the failing service, the error rate, the customer impact, and the on-call owner

Agent checks the message body against the bot's custom keyword setting so the send is not rejected

Agent posts an interactive card into the engineering group with the incident summary and a link to the ticket

Agent evaluates whether the severity crosses the threshold that would pull in other teams

The incident commander decides whether the war room group's business card is shared into the wider group, and the agent runs Share Chat only on a yes

What This Integration Enables

A Feishu custom bot is a webhook, not an API, and treating it as anything else will cost you a rebuild. It delivers messages into exactly one group chat, the group the bot was added to, and it delivers nothing back. There is no way to read the room, list members, fetch history, or receive events, which is why this connector has five send actions and no triggers. What you get in return is the lowest friction path into a Feishu group that exists: a URL from the group's own settings, no application registration, no review, no tenant credential.

FlowRunner agents use that slot for what it is good at. Plain text carries a terse alert. Rich posts carry structure and links. Images carry a rendered chart. Interactive cards built in the Feishu card builder carry anything that should read like a dashboard, and group business cards hand people an entrance to another room. Because the bot cannot hear a reply, any decision the flow depends on has to come back through a channel FlowRunner is listening on, which is exactly what a human-in-the-loop step provides. Feishu carries the announcement. The judgment arrives elsewhere and the flow resumes.

This connector targets Feishu on open.feishu.cn, the Chinese edition. If your team is on the international Lark Suite edition, the Lark Group Bot connector is the one to use; the two editions run on separate domains and a webhook from one will not work against the other.

Without FlowRunner

Incidents announced by hand Someone has to stop working the incident to write the update into the group

Updates arrive as plain text A wall of detail lands in the chat and the group has to parse it to find the impact

Access spreads informally People get pulled into the war room by whoever remembers to invite them

With FlowRunner

The group is told automatically The incident lands in the group as a formatted card the moment the ticket opens

Structured for reading Title, impact, owner, and link are laid out so the group sees the state in one glance

Access stays deliberate Widening the room to other teams is a decision a commander makes, not a rule that fires

Use Case Scenarios

Incident cards posted to the engineering group

A monitoring alert opens an incident and the agent assembles what the group actually needs: which service, how many requests are failing, which customers are affected, who is on call, and a link to the ticket in Jira. It posts that as an interactive card rather than as a paragraph, so the group reads the state instead of the narrative. As the incident moves, the agent posts follow up cards keyed to the same ticket. The engineers stay in the chat they were already in.

Release announcements with an at-everyone mention

When a release pipeline in GitHub finishes cleanly, the agent posts a rich post to the engineering group with the version, the changelog highlights, and a link to the release notes, using a mention when the release touches something the whole group needs to know about. The rich post format carries the links inline, so nobody has to leave the message to find out what shipped. A failed pipeline posts a different card, to a different bot, in the on-call group.

Daily operating summary as a card

Every morning a flow pulls yesterday's numbers from the systems that hold them, renders the two charts that matter, uploads them through the Feishu Open Platform image API, and posts a card into the management group with the figures and the images. Notably, the webhook itself cannot upload files: Send Image Message takes an image key, which means the upload step needs an application credential and happens before the send. Worth knowing at design time rather than at the first failed run.

Human-in-Loop Highlight

Four of this connector's five actions post content. Share Chat does something different: it drops another group's business card into the chat, complete with a join entry point, so anyone who sees it can walk into a group they were never invited to. That is an access change wearing a message's clothes, and the webhook offers no delete, so once the card is in the chat it stays visible to everyone in the room. The gate goes there. When an incident escalates and the agent's rule says to publicize the war room, it stops instead: "Severity is now P1 and the rule says share the incident war room card into the platform group, which is 240 people. The war room currently holds three engineers and the customer's account manager. Share it, share it into the engineering leads group instead, or keep it closed?" The incident commander answers, and Share Chat runs only if they said yes. Announcements the agent sends on its own. Doors it opens for other people, a person decides.

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 into the Feishu group the custom bot is installed in. Used for terse alerts and confirmations where the content is one fact and formatting would only get in the way.
Send Rich Post Message Sends a rich text post composed of a title and paragraphs of styled elements, including links and mentions. Used for release notes, daily reports, and any update where the group needs to click through to the source.
Send Image Message Sends an image to the group by its image key. The key comes from the Feishu Open Platform image upload API and requires an application credential, so the upload is a separate step ahead of the send rather than something the webhook can do on its own.

Cards and Sharing

Share Chat Posts a group business card into the chat, showing the shared group's name and avatar along with a join entry point. This widens who can reach another room, so it belongs behind a person rather than behind a rule.
Send Interactive Card Sends an interactive card built with the Feishu card builder. Used for incident summaries, status dashboards, and approval requests that need to be read at a glance. The card can carry buttons and links out to a decision surface, and the reply comes back to the flow through a channel FlowRunner can read.

Frequently Asked Questions

What can FlowRunner do with Feishu Group Robot?

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

Does connecting Feishu Group Robot to FlowRunner require OAuth?

Feishu Group Robot uses a custom authentication method to connect to FlowRunner.

Can Feishu Group Robot trigger a FlowRunner workflow automatically?

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

Start building with Feishu Group Robot

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

Start Building Free Talk to us