Feishu and DingTalk Form Notifications via Webhook

You built a form, but a dashboard alone is not enough when your team needs to act quickly. A Feishu or DingTalk form notification workflow sends each new submission into the group chat where sales, operations, or event teams already work.

Quick Answer

To send form submissions to Feishu, Lark, or DingTalk, you need a published form, a group bot webhook URL, and a form builder that can deliver each submission to that webhook. GenForms.ai supports this workflow through public forms, webhook-oriented delivery, and submission visibility, so the same form can collect data and notify the right team.

If you want a product entry point before the setup details, start with the Feishu and DingTalk form notifications workflow. If your main requirement is delivery reliability, compare it with the webhook form builder with retry logs.

Why You Need Form → IM Notifications

The problem with email notifications

Most form builders send you an email when someone submits. That's better than nothing, but:

• Email notifications get buried in your inbox
• They don't notify your team — only you see them
• No easy way to trigger a follow-up workflow from an email
• On mobile, email notifications are easy to miss

Why Feishu/Lark and DingTalk?

If you're running a business in China or serving Chinese users, Feishu (Lark) and DingTalk are where your team already lives.

• Feishu/Lark: Used by 10M+ organizations (ByteDance ecosystem)
• DingTalk: 600M+ users (Alibaba ecosystem)

Getting form submissions delivered as group messages means:

• Your whole team sees submissions in real time
• You can @mention the right person to follow up
• It feels native — no "checking another dashboard"

---

What You Need Before Starting

Requirement	Feishu/Lark	DingTalk
Group Bot	✅ Custom bot in group settings	✅ Custom bot in group settings
Webhook URL	Copied from bot settings	Copied from bot settings
Form builder with webhook support	✅ GenForms (Free plan)	✅ GenForms (Free plan)
Time needed	~5 minutes	~5 minutes

---

Step 1: Create a Group Bot in Feishu (Lark)

1. Open the Feishu/Lark group where you want to receive form notifications.

2. Click the group name (top left) → "Group Settings" (群组设置).

3. Click "Bots" (机器人) → "Add Bot" (添加机器人).

4. Select "Custom Bot" (自定义机器人).

5. Name your bot — e.g., "Form Notifications" (表单通知).

6. Copy the Webhook URL. This is the URL you'll paste into your form builder. Keep this private — anyone with this URL can send messages to your group.

7. (Optional) Set security rules:

   • IP whitelist: Only allow requests from specific IP addresses
   • Keyword verification: Messages must contain a specific keyword (e.g., "【New Form】")
   • Signature verification: Cryptographic signature (most secure, but requires code)

Recommendation: At minimum, set a keyword filter. This prevents someone from spamming your group if the webhook URL leaks.

---

Step 2: Configure the Webhook in GenForms

Note: This tutorial uses GenForms as the example because it supports webhooks on the free plan. Typeform requires the $83/month plan for webhooks.

1. Log into GenForms → open your form → click "Settings" (设置).

2. Scroll to "Webhook & API" → click "Add Webhook".

3. Paste your Feishu webhook URL into the URL field.

4. (Optional) Customize the payload:

   • By default, GenForms sends all form fields as a JSON payload.
   • You can customize the message format to make it readable in Feishu.

5. Click "Test Webhook" — you should see a test message appear in your Feishu group within 3 seconds.

6. Save. Your webhook is now live.

---

Step 3: Customize the Notification Message (Feishu Markdown)

By default, the webhook payload is raw JSON — not very readable in a chat group.

Feishu/Lark supports Markdown-formatted webhook messages. Here's a template you can use:

{
  "msg_type": "interactive",
  "card": {
    "config": { "wide_screen_mode": true },
    "header": {
      "title": { "tag": "plain_text", "content": "📝 New Form Submission" },
      "template": "blue"
    },
    "elements": [
      {
        "tag": "div",
        "text": {
          "tag": "lark_md",
          "content": "**Form:** Event Registration\n**Time:** {{submission_time}}\n**Name:** {{field.name}}\n**Email:** {{field.email}}\n**Message:** {{field.message}}"
        }
      },
      {
        "tag": "action",
        "actions": [
          {
            "tag": "button",
            "text": { "tag": "plain_text", "content": "View Details" },
            "url": "{{form_url}}",
            "type": "primary"
          }
        ]
      }
    ]
  }
}

In GenForms: Go to Webhook settings → "Advanced: Custom Payload" → paste the JSON above → use the variable picker to map your form fields.

---

Step 4: DingTalk Setup (Almost Identical)

DingTalk's custom bot setup is nearly the same:

1. Open the DingTalk group → click the "..." (more) button → "Group Settings" (群设置).
2. "Bots" (机器人) → "Add Bot" → "Custom Bot" (自定义机器人).
3. Copy the webhook URL.
4. Security settings: DingTalk supports keyword filtering and signing (recommended: set both).
5. Paste the webhook URL into GenForms (same as Step 2 above).

DingTalk Markdown Message Template

{
  "msgtype": "markdown",
  "markdown": {
    "title": "New Form Submission",
    "text": "## 📝 New Form Submission\n**Form:** Event Registration  \n**Time:** {{submission_time}}  \n**Name:** {{field.name}}  \n**Email:** {{field.email}}  \n[View Details]({{form_url}})"
  }
}

---

Step 5: Advanced — Error Handling & Retry

What happens if Feishu is down? Or your webhook URL is wrong?

GenForms has a built-in retry mechanism:

• Automatic retry: If a webhook POST fails (HTTP 5xx or timeout), GenForms retries up to 5 times over 72 hours.
• Audit log: In the form dashboard, click "Webhook Logs" — you can see every request, response, and retry attempt.
• Manual retry: If a submission's webhook failed and retries are exhausted, you can manually re-send from the audit log.

This is a huge advantage over other form builders — most don't show you webhook failure logs at all.

---

Alternative: Using Zapier or Make (No-Code Automation Platforms)

If your form builder doesn't support webhooks (e.g., Google Forms), you can use:

Platform	Difficulty	Cost
Zapier	⭐ Easy	Free for 100 tasks/month
Make (Integromat)	⭐⭐ Moderate	Free for 1,000 operations/month
n8n (self-hosted)	⭐⭐⭐ Harder	Free (self-hosted)

The workflow:

Form Submission → Zapier/Make → Format Message → Send to Feishu/DingTalk Webhook

Why GenForms is simpler: No middleware needed. The webhook goes directly from GenForms → Feishu. Fewer moving parts = fewer things that break.

---

FAQ

Can I send to both Feishu and DingTalk simultaneously?

Yes! In GenForms, you can add multiple webhooks to the same form. Just add a second webhook URL (DingTalk) and both will fire on every submission.

Is there a rate limit on Feishu webhooks?

Yes — Feishu limits custom bots to 20 messages/minute per bot. For most use cases, this is plenty. If you're expecting high-volume submissions, consider batching notifications or using Feishu's Open API instead.

Can I @mention someone in the Feishu group?

Yes — in the Markdown card payload, you can use "at": { "user_id": "ou_xxx" } to @mention a specific person. You'd need to know their Feishu user_id (get it from Feishu Open Platform admin console).

What if I use Slack or Discord instead?

GenForms webhooks work with any platform that accepts inbound webhooks — Slack, Discord, WeCom, Telegram, Microsoft Teams, or your own server. GenForms has native provider support for Feishu, DingTalk, WeCom, and Slack bots. Just paste the platform's webhook URL.

Why doesn't Google Forms support webhooks?

Google Forms doesn't have native webhook support. You'd need to use Google Apps Script to write a custom webhook function (requires coding), or use Zapier as a middleware layer.

---

The Simplest Setup (Recap)

1. Create a custom bot in your Feishu/DingTalk group → copy the webhook URL.
2. Log into GenForms (free plan supports webhooks!) → open your form → Settings → Add Webhook.
3. Paste the URL → click "Test" → confirm the message appears in your group.
4. (Optional) Customize the message format using the JSON template above.
5. Done. Every form submission now notifies your team in real time.

---

Want a form builder that supports webhooks on the free plan (no $83/month paywall)? → Try GenForms for free — webhooks and AI included, no credit card required.

Next steps

If you are setting up team notifications, start with the Feishu and DingTalk notification workflow and compare it with the broader form builder with webhook guide. You can also browse ready-to-use form templates before publishing your first workflow.

Try This Workflow

Start from the Feishu and DingTalk form notifications workflow, then publish a form and test one real notification before sending it to users.