diff --git a/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.assets/1.png b/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.assets/1.png
new file mode 100644
index 0000000000..6e39249bc3
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.assets/1.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.assets/2.png b/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.assets/2.png
new file mode 100644
index 0000000000..af6e5f2b6b
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.assets/2.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.assets/3.png b/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.assets/3.png
new file mode 100644
index 0000000000..675e2155fe
Binary files /dev/null and b/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.assets/3.png differ
diff --git a/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.md b/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.md
new file mode 100644
index 0000000000..b27fc9bde5
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs-guides/current/solution/openclaw.md
@@ -0,0 +1,87 @@
+---
+title: 'How to Integrate OpenClaw'
+sidebar_position: 8
+
+---
+
+# How to Integrate OpenClaw
+
+This document is intended for OpenIMSDK users. It explains how to connect OpenIMServer through OpenClaw Gateway and verify the integration by sending the first message.
+
+## 1. Prerequisites
+
+- You have already [deployed OpenIMServer and ChatServer](../gettingStarted/dockerCompose), deployed and started OpenClaw Gateway, and can run the `openclaw` command on the machine where Gateway is running.
+
+## 2. Register an OpenClaw User
+
+### 1. Register a user
+
+Log in to the admin console. The default address is `http://server_ip:11002`, where `server_ip` is the IP address where `open-im-server` is deployed.
+
+Select User Management -> User List, then click **Create New User** on the right:
+![image-20260310115043272](./openclaw.assets/1.png)
+
+Enter the account information:
+
+![image-20260311110212683](./openclaw.assets/2.png)
+
+### Get an admin token
+
+Refer to the [Get Admin Token](../../restapi/apis/authenticationManagement/getAdminToken) document to obtain an admin token.
+
+### Get a user token
+
+After obtaining an admin token, refer to the [Get User Token](../../restapi/apis/authenticationManagement/getUserToken) document to issue a login token for the specified user. Set `userID` to the `userID` of the user you just registered, and set `platformID` to 12 (which indicates bot).
+
+## 3. Install the OpenIM Channel Plugin
+
+```bash
+openclaw plugins install @openim/openclaw-channel
+```
+
+Plugin URL: https://www.npmjs.com/package/@openim/openclaw-channel
+
+## 4. Enable the Plugin and Configure OpenIM Channel
+
+### Method A: Interactive setup (recommended)
+
+```bash
+openclaw openim setup
+```
+
+Follow the prompts to fill in `token`, `wsAddr`, `apiAddr`, and other information.
+
+### Method B: Edit the configuration file directly
+
+Edit: `~/.openclaw/openclaw.json`
+
+Example:
+
+```json
+{
+  "channels": {
+    "openim": {
+      "accounts": {
+        "default": {
+          "enabled": true,
+          "token": "your_token",
+          "wsAddr": "ws://127.0.0.1:10001",
+          "apiAddr": "http://127.0.0.1:10002"
+        }
+      }
+    }
+  }
+}
+```
+
+## 5. Verification: Send the First Message
+
+In OpenIM, search for the corresponding bot account by `userID`, then send a message to verify whether it can auto-reply.
+
+If the other side successfully receives the message, OpenClaw has completed integration with OpenIM.
+
+![image-20260311115813414](./openclaw.assets/3.png)
+
+## 6. FAQ
+
+- **OpenIM is not connected**: This is usually caused by incorrect `token`, `wsAddr`, or `apiAddr` configuration, or by network inaccessibility. First verify the configuration, then troubleshoot based on OpenClaw Gateway logs.