Integration

WeCom Group Robot integration

WeCom group robot webhook, the incoming webhook a WeCom (Enterprise WeChat) group exposes so an external system can post into it. Send text, markdown, image, news, file, voice and template card messages into the group, and upload a voice or file first to obtain the media identifier those two message types need. This covers the group-robot webhook ONLY, it is not the WeCom platform API: the platform API is not modelled here because its access_token has to be minted from a corp id and secret and expires every two hours, which a stored static credential cannot satisfy. There is therefore no access to contacts, users, departments or conversations, only posting into the one group the webhook key belongs to.

Connect WeCom Group Robot How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in WeCom Group Robot.Built from the 2 WeCom Group Robot tools below, on the connection you add once.

Common WeCom Group Robot use cases

uploading a PDF report before posting it into a WeCom group
posting a build or alert notification into a WeCom team group
sending a daily report into a group chat

What you can do with WeCom Group Robot

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Media, 1 operation

upload_mediaUpload mediaPOSTUploads a file or voice clip so a later message can reference it by media identifier.

Message, 1 operation

send_messageSend messagePOSTPosts a text, markdown, image, news, file, voice or template card message into a WeCom group.

Use WeCom Group Robot from Claude Code, Cursor or Codex

Connect WeCom Group Robot in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its WeCom Group Robot operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect WeCom Group Robot

Create your workspace
Sign up free. Nothing to install.
Connect WeCom Group Robot once
Add your WeCom Group Robot connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

WeCom Group Robot integration FAQ

What can you do with the WeCom Group Robot integration?

LiveContext exposes 2 operations on WeCom Group Robot, covering media and message. Common uses include uploading a PDF report before posting it into a WeCom group, posting a build or alert notification into a WeCom team group and sending a daily report into a group chat.