Skip to main content

๐Ÿ’ฌ DingTalk Integration

๐Ÿ‘ค Who it's for: Companies using DingTalk
โฑ๏ธ Read time: ~5 minutes
๐Ÿ’ก In one line: Bring YingClaw into your DingTalk workspace โ€” your enterprise AI assistant is always on standby.

Connect YingClaw to DingTalk via Stream Mode WebSocket for real-time messaging without needing a public IP.


Overviewโ€‹

YingClaw uses DingTalk's Stream Mode to establish a WebSocket connection with DingTalk's gateway, enabling message push without a public IP address.

ScenarioDescription
๐Ÿ’ผ Enterprise AssistantEmployees consult AI directly in DingTalk
๐Ÿ“‹ Workflow AutomationApprovals, notifications, data queries in one step
๐Ÿ“ข Scheduled PushDaily/weekly reports sent to DingTalk groups

Setupโ€‹

1. Get DingTalk App Credentialsโ€‹

Go to DingTalk Open Platform and create an internal enterprise app to get:

  • Client ID: Your application's unique identifier
  • Client Secret: Your application's secret key

2. Configure in YingClawโ€‹

Log into the YingClaw Web Console, go to "Channels", enable DingTalk, and fill in:

ParameterDescription
client_idClient ID from DingTalk Open Platform
client_secretClient Secret from DingTalk Open Platform
allowed_usersEmployee allowlist, * means all employees

3. Start the Channelโ€‹

After saving, YingClaw automatically connects via Stream Mode. No callback URL or public IP is needed.


Message Interactionโ€‹

Private Chatโ€‹

Employees send messages directly to the Bot. YingClaw responds in real time, supporting:

  • ๐Ÿ’ฌ Intelligent Q&A and conversation
  • ๐Ÿ“Š Data queries and report generation
  • ๐Ÿ“ Document writing and editing
  • โฐ Schedule management and reminders

Group Chatโ€‹

Add the Bot to a DingTalk group, then @ mention it to trigger a response.

User Allowlistโ€‹

channels:
dingtalk:
allowed_users:
- "manager001" # Only specific employees
# - "*" # Allow all employees

Notesโ€‹

  • Stream Mode requires no public IP โ€” ideal for intranet deployments
  • Use an internal enterprise app type โ€” data stays within your organization
  • In groups, configure @-mention-only to avoid noise

Next Stepsโ€‹