Grok BotWorkPlanningAI score · 80/100AI-assisted edit · no obvious prompt-injection riskX

Connect Grok Bot Team to Feishu: Scan-to-Create App, Webhook Trigger, and Multi-Bot Group Collaboration

Configure Grok Bots as standalone Feishu bots with scan-to-create apps and webhook triggers for both DM and group chat

ExperiencedStepsWorkflowTip
Who
Teams already using Grok Bot and deeply integrated with Feishu
You get
Multiple Grok Bots become independent Feishu bots, supporting direct messages, group chat, @-mentions, and cross-bot delegation
You need
Grok Bot

Constraints

Prerequisites: Grok Bot account, Feishu CLI installed and bound to an enterprise, and a virtual machine with Python. Each bot needs one Feishu app, one VM forwarding program, and one doorbell trigger. No public IP required; all traffic uses Feishu long-connection outbound.

What they did

Author cgnot996 configured three Grok Bots (Editor-in-Chief, Bookkeeping Manager, VM Service Manager) as independent Feishu bots. The first bot created a Feishu app via QR scan and configured a doorbell trigger. A 'Feishu App Manager' bot was then created to batch-build the remaining apps. Finally, all three bots were added to a single Feishu group for @-mentions and cross-bot collaboration.

How it went

Two-way DM communication responded within one second after configuration. After fixing permissions and @-mention rules, all three bots responded correctly in group chat and could delegate tasks to each other (author_report). The forwarding program auto-recovered in about 9 seconds after being force-killed.

Worth knowing

Known limitations and pitfalls (author_report): 1) Initial 7 permissions are insufficient for group messages; ensure the default 14 are granted. 2) Feishu '@all' does not count as '@bot'; the forwarding program must handle this separately. 3) Commands relayed by one bot are not treated as direct user instructions; sensitive operations should use Feishu card buttons for confirmation. 4) The forwarding program must use the virtual environment's Python absolute path, not system python3. 5) Bots with existing triggers need a separate 'Feishu Message' trigger so casual chat isn't misprocessed. 6) The forwarding program has a 5-second auto-restart loop and 5-minute health check; Feishu auto-replays messages after reconnect—do not manually resend. 7) Template link https://x.ai/bot/AJpUlCwa8tyMX7L5UHnuY strips secrets and personal info, but VM scripts must be rebuilt after import. 8) Not tested by this site; all claims are author-reported.

Steps

  1. Have Grok Bot generate a scan-to-create app link

    Ask the target Grok Bot (e.g., Editor-in-Chief) to call the Feishu official Python SDK's scan-to-create-app feature. The bot sends a one-time creation link and QR code in DM. The link is single-use and tied to you—do not forward it, or the app credentials will be exposed.

  2. Scan QR to create the Feishu app and confirm permissions

    Open the link. The app name and avatar are pre-filled; click Create. After the security notice, go to the permissions and events page—the required permissions (14 by default) and events are pre-configured; just confirm. No manual enablement of bot capability, permission setup, long-connection selection, or publishing is needed.

  3. Configure the doorbell trigger and hand over secrets

    After creation, the system returns app credentials (App ID / Secret) automatically—no manual copy needed. Then create a 'Feishu Message' doorbell trigger for the target bot in Grok Bot. Copy the trigger webhook address and secret, and paste them into Grok Bot's encrypted input field. The bot cannot read these values directly; the user must hand them over manually.

  4. Test two-way DM communication

    Find the newly created bot in Feishu and send a test message. The backend should forward to the trigger in under one second, and the bot should reply in the conversation. If the trigger wasn't connected during the first test, the bot may not reply, but it can use that message to whitelist you.

  5. Use Feishu App Manager to batch-create apps

    Create a 'Feishu App Manager' bot to batch-create Feishu apps for other bots. The manager maintains a registry table (Bot ↔ App ↔ Secret location ↔ Doorbell trigger) and generates one-time QR links valid for one hour. Ensure Feishu CLI is switched to the bound enterprise, then scan to create. The manager also notifies each target bot to create its doorbell trigger and prompts you to fill the encrypted fields with address and secret.

  6. Add bots to a group and configure group collaboration rules

    Create a Feishu group on desktop and add multiple bots. Ensure the app permissions include 'Receive all @bot messages in groups' (one of the 14 default permissions). In the forwarding program, configure @-mention rules: respond only to @self or @all, preventing multiple bots from replying simultaneously or missing messages. Test by @all or mentioning a specific bot; verify each bot claims its task correctly. Further test cross-bot delegation (e.g., @Editor-in-Chief to ask VM Service Manager to post the service registry).

Prompt you can copy

Reference prompt · Editorial suggestion。Confirm the destination, input variables and output format before use.

This block is the prompt. Ads are never placed here.

No prompt needed — just follow the steps.

Follow the steps in Grok Bot and Feishu Open Platform; no additional prompt required.

Source

（中文）Grok Bot 团队接飞书：扫码建应用→门铃 webhook→飞书应用管家批量→群内 @ 派活 · cgnot996 · X · 2026-10-11T11:41:02.000Z

Comments & feedback

Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.

Loading…

    Related