Skip to main content

YingClaw Notification Push Setup Guide: Send Task Results to WeChat and DingTalk Automatically

When a digital employee finishes a task, the result sitting on your computer screen is only half the story — you still have to go check it, which is not real automation. YingClaw, the AI agent platform from Yingying Zhi, has notification push built in, supporting WeChat, DingTalk, Feishu, WeCom, QQ, and other mainstream IM channels. The moment a task finishes, the result lands in the chat window on your phone. This tutorial walks you through configuring notification push so your digital employee stops "waiting for you to check" and starts "coming to you on its own."

What Notification Push Can Do

Let's first clarify the scenarios. Notification push solves the question of "how results reach you," with three typical use cases:

  • Result delivery: after a task completes, send the summary table, report, or key data directly to a group or private chat
  • Anomaly alerts: immediately remind you when a task fails, data looks abnormal, or a threshold is exceeded
  • Scheduled broadcasts: combined with scheduled tasks, push yesterday's core data to you every morning

A common example: a sales team wants to see customers not contacted for over 7 days every morning. YingClaw can pull the data, generate the list, and send the result straight to a DingTalk group — no need to open your computer.

Before You Configure

Before setting up notification push, confirm three things:

  1. You have an account on the target IM and can create a group or bot. Personal WeChat and WeCom connect differently; DingTalk and Feishu usually require creating a group bot to get a Webhook address
  2. Decide the push target: your own private chat, or a team group. For team collaboration, groups are better for information sharing
  3. Prepare the receiver info: channel type, group identifier, or bot address — you will need these during configuration

Connecting Channels: WeChat, DingTalk, Feishu, WeCom, QQ

YingClaw supports multiple IM channels with a consistent approach: add a notification channel on the platform, fill in the channel's connection info, verify connectivity, and start using it.

DingTalk: add a "custom bot" in your DingTalk group, get the Webhook address, fill it into YingClaw's notification channel config, save, and send a test message to verify.

WeCom: add a group bot in a WeCom group, get the Webhook address, and fill it in. WeCom bots also support mentioning members by department or tag.

Feishu: add a custom bot in your Feishu group, get the Webhook address, and configure it. For Feishu's signature verification, fill in the secret key as described in the official docs.

Personal WeChat / QQ: follow the guided flow in the YingClaw client to complete login authorization and bind the channel to your account. Task results can then be delivered straight to your private chat.

After configuration, the platform usually offers a "send test message" button — receiving the message means the channel works.

Attaching Push to a Task: Just One Sentence

Once channels are set up, using them is simple — no code required. Just tell the digital employee where to send the result when you assign the task. For example:

Every morning at 9 AM, summarize yesterday's sales data into a report and send it to the DingTalk "Daily Sales" group.

Or be more specific about the target:

Check these 5 websites for updates, and if there are any, compile the links and send them to my WeCom.

YingClaw automatically packages task results into a chat-friendly form (text summary, file, or link) and delivers them to the channel you specified. If a task fails, you can also configure error messages to be pushed to an alert group, so you know immediately when something goes wrong.

Example Scenarios

  • Customer follow-up reminders: every Monday morning, send the list of customers not contacted for over 7 days to the sales group
  • Daily and weekly reports: every morning at 9 AM, push yesterday's core business metrics to the management group
  • Competitor monitoring: when a competitor's website updates, push the changes to you right away
  • Task failure alerts: when a digital employee errors out, send the error details to the tech group
  • Approval flow notifications: when a new expense report awaits approval, notify the corresponding approver

FAQ

Can one task push to multiple channels? Yes. You can configure several notification channels and specify where each result goes in the task. For example, send the daily report to a DingTalk group and a full version to your WeCom private chat.

How do notification push and scheduled tasks relate? They complement each other. Scheduled tasks decide "when to run"; notification push decides "where results go." The combination — scheduled task plus push — is the most common automation setup, such as generating a daily report every morning and pushing it to a group.

Can push leak sensitive data? YingClaw emphasizes local deployment and data control — what gets pushed is up to you. For sensitive information, push only summaries or desensitized key metrics and keep full data in the local system.

Once notification push is configured, your digital employee is truly "embedded in your workflow" — you no longer need to chase results; important information comes to you. This is exactly the philosophy behind Yingying Zhi's digital employee: AI should not be a tool you must actively ask, but a colleague that actively watches and reports for you.