WeCom Bot

Operate WeCom Bot through your OOMOL-connected account. This skill calls the wecom_bot connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Category: Communication. Exposes 5 action(s).

Running an action

Assume the user has already installed the oo CLI, signed in, and connected WeCom Bot. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "wecom_bot" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "wecom_bot" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with oo connector schema before constructing --data.

Available actions

• send_image_message — Send an image message through the WeCom bot webhook.
• send_markdown_message — Send a markdown message through the WeCom bot webhook.
• send_markdown_v2_message — Send a markdown_v2 message through the WeCom bot webhook.
• send_news_message — Send a news message through the WeCom bot webhook.
• send_text_message — Send a text message through the WeCom bot webhook.

Safety

• Read actions (get / list / search) are safe to run directly.
• Create, update, send, or post actions change WeCom Bot state — confirm the exact payload and effect with the user before running.
• Delete or remove actions are destructive — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: ):

```bash

curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux

```

```powershell

irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell

```

• Not signed in / authentication error — sign in to your OOMOL account once:

```bash

oo auth login

```

• scope_missing / credential_expired / app_not_ready / app_not_found — WeCom Bot is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

```text

https://console.oomol.com/app-connections?provider=wecom_bot

```

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• WeCom Bot homepage: https://work.weixin.qq.com