DingTalk Integration

Enforce inbound-only DingTalk replies and schedule reminders within the thread.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rocky2431/hiveclaw --skill dingtalk-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: DingTalk Integration
Source: https://github.com/rocky2431/hiveclaw/tree/main/backend/app/templates/system_skills/dingtalk-integration
Command: npx skills add https://github.com/rocky2431/hiveclaw --skill dingtalk-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DingTalk channel acts as an inbound-only bridge; you reply in the current conversation and the channel handler delivers it back. Proactive outbound actions or user lookups are not available.

Core Features & Use Cases

  • Inbound-only DingTalk channel; reply in the current thread and rely on the channel handler to forward messages back.
  • Set up follow-ups and reminders using set_trigger, list_triggers, and related workflows with explicit reasons, all within the thread.
  • Coordinate with other digital employees via send_message_to_agent when appropriate, without leaving the current conversation.

Quick Start

Reply in the current DingTalk thread and, when needed, schedule a follow-up using set_trigger.

Frequently Asked Questions about DingTalk Integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle inbound DingTalk channel messages and reply within the same thread?

To handle inbound DingTalk channel messages, reply directly in the current conversation thread. The channel handler acts as an inbound-only bridge and automatically delivers your response back to the user.

Can I schedule follow-up reminders for DingTalk conversations using triggers?

Yes, you can schedule follow-up reminders for DingTalk conversations by using the set_trigger and list_triggers tools. You must provide explicit reasons for the trigger and manage the workflow entirely within the current thread.

Why does my DingTalk integration fail when trying to perform outbound user lookups?

DingTalk integration restricts outbound user lookups because the channel operates as an inbound-only bridge. Proactive outbound actions and external user searches are prohibited to prevent unauthorized actions or external communications.

How do I coordinate with other digital employees from a DingTalk channel conversation?

You can coordinate with other digital employees from a DingTalk conversation by using the send_message_to_agent tool. This allows internal agent communication without leaving the current inbound-only thread.

What are the limitations of using an inbound-only DingTalk channel for workflow automation?

The limitation of an inbound-only DingTalk channel is that it prohibits proactive outbound actions and user lookups. You must rely on the channel handler to forward messages back and manage all workflows within the current thread.