Integration

DingTalk Custom Robot integration

DingTalk custom robot webhook, the incoming webhook a DingTalk group exposes so an external system can post into it. Sends text, link, markdown, action card and feed card messages into the one group the webhook token belongs to. This works ONLY when the robot was created with the custom keyword or the IP allowlist security mode: the third mode, signature, requires an HMAC-SHA256 signature recomputed from a fresh timestamp on every single request, which a stored static credential cannot produce, so a signed robot will be rejected and is not modelled here. This is the group webhook only, not the DingTalk platform API, whose access token has to be minted from an app key and secret and expires every two hours.

Connect DingTalk Custom Robot How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in DingTalk Custom Robot.Built from the 1 DingTalk Custom Robot tool below, on the connection you add once.

Common DingTalk Custom Robot use cases

posting a build or alert notification into a DingTalk team group
sending a daily summary into a group chat

What you can do with DingTalk Custom 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.

send_messageSend messagePOSTPosts a text, link, markdown, action card or feed card message into a DingTalk group.

Use DingTalk Custom Robot from Claude Code, Cursor or Codex

Connect DingTalk Custom Robot in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its DingTalk Custom 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 DingTalk Custom Robot

Create your workspace
Sign up free. Nothing to install.
Connect DingTalk Custom Robot once
Add your DingTalk Custom 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.

DingTalk Custom Robot integration FAQ

What can you do with the DingTalk Custom Robot integration?

LiveContext exposes 1 operation on DingTalk Custom Robot, covering message. Common uses include posting a build or alert notification into a DingTalk team group and sending a daily summary into a group chat.