--- title: "RockChinQ (@rockchinq) | Hashnode" description: "Engineer @Dify. Read the latest articles by RockChinQ on Hashnode." url: "https://hashnode.com/@rockchinq" --- @rockchinq # RockChinQ @rockchinq · Osaka, Japan · Joined February 2026 Engineer @Dify ### [QQ friend requests and group invites: two approvals, one Agent](https://langbot.hashnode.dev/qq-friend-requests-and-group-invites-two-approvals-one-agent?utm_source=hashnode&utm_medium=feed) Scenario A QQ bot mostly does not chat; it handles two requests: a stranger asks to add it as a friend, or it gets pulled into a group. A pipeline built for "message in → reply out" cannot catch them 6 min read · [langbot.hashnode.dev](https://langbot.hashnode.dev/qq-friend-requests-and-group-invites-two-approvals-one-agent?utm_source=hashnode&utm_medium=feed) [Oct 21](https://hashnode.com/posts/qq-friend-requests-and-group-invites-two-approvals-one-agent/6ad81f495f94f51902b31876) ### [One Telegram group, three event routes: welcome, rules Q&A and moderation each get their own Agent](https://langbot.hashnode.dev/one-telegram-group-three-event-routes-welcome-rules-q-a-and-moderation-each-get-their-own-agent?utm_source=hashnode&utm_medium=feed) Scenario A Telegram community group has three chores — greet joiners with the two rules, answer "how do I configure this", deal with ad spam on the spot — and today all three ride one bot: one pipelin 6 min read · [langbot.hashnode.dev](https://langbot.hashnode.dev/one-telegram-group-three-event-routes-welcome-rules-q-a-and-moderation-each-get-their-own-agent?utm_source=hashnode&utm_medium=feed) [Oct 21](https://hashnode.com/posts/one-telegram-group-three-event-routes-welcome-rules-q-a-and-moderation-each-get-their-own-agent/6ad81ea9964d2ce65f02ced6) ### [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 6 min read · [langbot.hashnode.dev](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) [Oct 20](https://hashnode.com/posts/wiring-dify-into-wecom-customer-service-install-a-runner-plugin-let-an-agent-own-message-received/6ad6cfe6583b447f120f2420) ### [Wiring n8n into Slack: @mention the bot to run an automation workflow](https://langbot.hashnode.dev/wiring-n8n-into-slack-mention-the-bot-to-run-an-automation-workflow?utm_source=hashnode&utm_medium=feed) Scenario The team works in Slack; the automations live in n8n. Sending a release notice means someone leaving the channel, opening n8n, clicking Execute and pasting the result back. Making the convers 6 min read · [langbot.hashnode.dev](https://langbot.hashnode.dev/wiring-n8n-into-slack-mention-the-bot-to-run-an-automation-workflow?utm_source=hashnode&utm_medium=feed) [Oct 20](https://hashnode.com/posts/wiring-n8n-into-slack-mention-the-bot-to-run-an-automation-workflow/6ad6ce9b5d060285df8ea5a9) ### [Making a Bot Production-Ready: Operation Logs, 2FA and Signed Plugins](https://langbot.hashnode.dev/making-a-bot-production-ready-operation-logs-2fa-and-signed-plugins?utm_source=hashnode&utm_medium=feed) Scenario Before a bot serves real users, an operator faces three questions: who changed the provider key yesterday and deleted that pipeline; who can log in, and is there a second door besides the pas 6 min read · [langbot.hashnode.dev](https://langbot.hashnode.dev/making-a-bot-production-ready-operation-logs-2fa-and-signed-plugins?utm_source=hashnode&utm_medium=feed) [Oct 19](https://hashnode.com/posts/making-a-bot-production-ready-operation-logs-2fa-and-signed-plugins/6ad57b1e39cde4bbff59ac8a)