Send tasks to your bot from WeChat: a ClawBot-to-Webhook-routine setup brief

(Translated from the author's Chinese.) Please connect Grok Bot to WeChat ClawBot so I can send you tasks in WeChat and get replies. Check the prerequisites first, then configure step by step; wherever I need to scan a code, enter credentials or confirm an account, stop and explain what to do.

1. First check whether this workspace supports Webhook Routines, running a relay program, and storing credentials securely. If anything is missing, explain why; don't pretend it's done.

2. Research WeChat ClawBot's iLink integration and verify getupdates for receiving, sendmessage for replying, and the QR-code login flow. Prefer reusing a vetted implementation, and tell me which approach you chose, its source and the permissions it needs. The relay only makes outbound requests and opens no extra public port on this machine.

3. Create a Webhook-triggered Routine named "WeChat task inbox". Tell me where to get the Webhook URL and key. Receive them only through a private credential input the platform actually supports; if there isn't a secure one, stop. Don't ask me to paste secrets into normal chat.

4. Configure forwarding from WeChat messages to the Routine and replies back. Handle only the one WeChat user I explicitly allow and reject everyone else by default; if an empty list means "allow all" in the implementation, change it to an explicit list. Process duplicate messages only once, and reply in plain text.

5. Once I confirm WeChat ClawBot is enabled, show the QR code for this binding and any backup login method. Wait for me to scan and confirm; if the code expires, generate a new one.

6. After binding, remind me to send one message in the ClawBot chat first to establish the context_token needed for replies. Then run one full test: receive a message, trigger the Routine, reply in WeChat.

7. Check how the relay recovers after a restart. Keep only one receiving process per account; if the login credential expires, tell me clearly to rebind instead of looping on QR scans.

Finally report: binding status, listener status, whether the Routine was triggered, whether the test reply arrived, and which steps remain. Never include any secret in the report.