How to Send Form Notifications to a Lark or Feishu Bot Using Webhooks

Real-time notifications are essential for keeping operations teams and marketing squads aligned. When a prospect requests a sales callback, signs up for an event, or submits a bug report, every minute of delay increases the chances of customer drop-off. Pushing these submissions instantly into your group chat ensures that the right team member can respond immediately.

For teams using Lark (the international version of Feishu) or Feishu for team communication, setting up a custom webhook group bot is one of the most effective ways to establish a notification stream. In this guide, we will walk through the exact steps to connect form submissions to a Lark or Feishu chat bot, configure the message payload, and ensure delivery reliability.

Why Group Bot Notifications Matter

Many traditional forms rely on email alerts to notify administrators of new responses. However, inbox clutter makes it easy for important leads to get lost. A chat notification places the information directly into a shared workspace, making it collaborative and visible.

By using a webhook-ready form builder workflow, you can trigger an automated push request the instant a respondent hits submit. This enables several team-centric behaviors:

1. Shared Ownership: Any team member in the channel can claim a lead or comment on a submission.
2. Speed to Response: Instant messaging alerts trigger immediate notifications on mobile or desktop devices.
3. Structured Context: A custom bot can format the form data as a clean card, showing the key details (like budget, company size, and main pain point) at a single glance.

If you are currently evaluating other form tools, keep in mind that many platforms charge a premium for custom HTTP post integrations. You can review how this pricing compares on our typeform alternatives comparison article.

Step 1: Create a Webhook Bot in Lark or Feishu

To generate a webhook destination URL, you need administrator or bot-creation permissions in the target group chat:

1. Open the Chat Settings: Go to the Lark or Feishu desktop application, navigate to the group chat where you want to receive alerts, click the settings icon in the top right, and select "Group Bots".
2. Add a Custom Bot: Click "Add Bot", choose "Custom Bot" (often labeled as Webhook Bot), and click "Add".
3. Configure Bot Identity: Give the bot a descriptive name (like "GenForms Lead Alert") and optionally upload a logo.
4. Copy the Webhook URL: Once saved, Lark will provide a unique HTTP endpoint URL. Copy this URL. Keep it secure, as anyone with this link can post messages to your channel.
5. Set Security Settings: Lark and Feishu require at least one security configuration: custom keywords, IP whitelisting, or a signature verification secret. If your form builder supports basic headers, choose "Custom Keyword" and add a keyword that will appear in your form alerts, or choose "Signature Verification" if you are using custom script routing.

Step 2: Set Up the Webhook Delivery in Your Form Builder

With the webhook URL ready, the next step is routing submissions from your form builder:

1. Configure Webhook Settings: In your form builder dashboard, go to the Integrations or Webhook section.
2. Enter the Endpoint: Paste the copied Lark/Feishu webhook URL.
3. Map the Payload: Lark and Feishu bots require a specific JSON structure to display messages. A simple text message payload looks like this:

   {
     "msg_type": "text",
     "content": {
       "text": "New form submission received! Email: {email}"
     }
   }
   

   For more advanced layouts, Lark supports "post" and "card" message types, allowing you to add colored headers, structured tables, and button links.

If your webhook target server experiences brief downtime, you will want a system that automatically buffers the message and retries delivery. To understand how automated queue recovery functions, check out our form builder with webhook guide for technical details.

Recommended Form Fields for Team Notifications

To prevent chat channel noise, avoid sending long walls of text. Only send the vital details that require action. We recommend using these fields in your intake form:

• Name: Who submitted the request.
• Email Address: Direct contact point for routing.
• Company/Project: Basic context for business qualifying.
• Inquiry/Message: The open-ended question that explains what they need.

By keeping the notification payload concise, your team can review submissions on mobile devices without scrolling through pages of data.

Common Pitfalls to Avoid

• Incorrect Message Format: Lark and Feishu will reject webhook calls if the top-level keys like "msg_type" or "content" are missing or misconfigured. Always test the payload using a tool like Postman or Curl first.
• Security Settings Mismatch: If you configured a "Custom Keyword" security rule, ensure that the exact keyword is present in the text field of your form's JSON payload. If the keyword is missing, the bot will return an error code.
• Lack of Retry Support: If your receiving bot endpoint returns a 502 or 429 status code during a high-traffic campaign, you risk losing notification signals. Ensure your form builder keeps audit logs of webhook transactions.

Next Steps to Build This

You can build a fully automated notification pipeline in a few minutes. Start by opening the webhook-ready form builder tool, describe your form fields to our AI, paste your Lark/Feishu webhook URL in the settings panel, and send a test submission to verify the live notification card in your group chat.