---
title: "Discussion on \"Wiring Dify into WeCom Customer Service: install a Runner plugin, let an Agent own message.received\" | Hashnode"
description: "Discussion on \"Wiring Dify into WeCom Customer Service: install a Runner plugin, let an Agent own message.received\". Scenario\nThe knowledge base, prompts and tools live in a Dify application; the WeCom customer-service side only answers customers. Today every question is retyped into Dify's chat box and the answer c"
url: "https://hashnode.com/posts/wiring-dify-into-wecom-customer-service-install-a-runner-plugin-let-an-agent-own-message-received/6ad6cfe6583b447f120f2420"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Wiring Dify into WeCom Customer Service: install a Runner plugin, let an Agent own message.received](https://langbot.hashnode.dev/wiring-dify-into-wecom-customer-service-install-a-runner-plugin-let-an-agent-own-message-received?utm_source=hashnode&utm_medium=feed)

Scenario The knowledge base, prompts and tools live in a Dify application; the WeCom customer-service side only answers customers. Today every question is retyped into Dify's chat box and the answer c

Oct 20 · 6 min read · langbot.hashnode.dev  
Read the article

## Written by

[RockChinQ](https://hashnode.com/@rockchinq)

@rockchinq · Osaka, Japan

  
[View profile](https://hashnode.com/@rockchinq)

Engineer @Dify

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
