@mondaycom/openclaw-monday
Connect OpenClaw and NemoClaw agents to monday.com. This plugin receives webhook triggers (mentions, assignments, chat messages) and routes them to your OpenClaw agent, then responds via the monday.com API.
How it works
- Mentions/Assignments: Plugin acknowledges immediately, processes the message asynchronously, and posts the agent's response back to the relevant board item via the monday.com GraphQL API.
- Chat: Plugin holds the HTTP connection open, streams the agent's response back as SSE, enabling real-time chat in the monday.com sidebar.
Session continuity is automatic -- same board item = same conversation for triggers, same chat thread = same conversation for chat.
Setup
1. Create a custom agent on monday.com
Follow the custom agent setup flow in the monday.com AI agents builder. You'll receive:
- A signing secret (for HMAC webhook verification)
- An API token (for posting responses back to monday.com)
2. Install the plugin
openclaw plugins install clawhub:@mondaycom/openclaw-monday
3. Configure
Add to your ~/.openclaw/openclaw.json:
{
plugins: {
"@mondaycom/openclaw-monday": {
"mondayApiToken": "<your-monday-api-token>",
"signingSecret": "<your-signing-secret>",
"agentId": "main" // Which OpenClaw agent handles monday.com messages
}
}
}
4. Expose your OpenClaw instance
monday.com needs to reach your OpenClaw webhook endpoint. Two built-in options:
Option A — Tailscale Funnel (built into OpenClaw):
Add to your OpenClaw gateway config:
{
"gateway": {
"tailscale": {
"mode": "funnel"
}
}
}
Your public URL will be https://<hostname>.tail*.ts.net/hooks/monday.
Option B — Cloud / VPS deployment:
If OpenClaw runs on a cloud server with a public IP or domain, set bind: "lan" in your gateway config so it listens on all interfaces:
{
"gateway": {
"bind": "lan"
}
}
Your callback URL will be https://<your-server>/hooks/monday.
5. Register your callback URL
Register your public URL with monday.com using the GraphQL mutation provided in the setup instructions:
mutation {
register_custom_agent_callback(
app_id: <your-app-id>,
callback_url: "https://<your-public-url>/hooks/monday"
) {
success
}
}
NemoClaw
This plugin works identically on NemoClaw deployments. NemoClaw runs OpenClaw inside a sandboxed environment, so the plugin installs and operates the same way.
The only additional step is allowing outbound network access to the monday.com API:
nemoclaw policy-add api.monday.com
Architecture
monday.com OpenClaw / NemoClaw
--------- -------------------
User mentions agent
|
v
POST /hooks/monday ----------> Plugin receives webhook
(HMAC signed) |
| Verify HMAC signature
| Build session key
|
[Chat?] ----Yes----> Route to agent session
| Stream SSE response back
| to monday.com chat UI
|
[Trigger?] --Yes---> Acknowledge HTTP 200
Route to agent session
Agent processes async
POST response via
monday.com GraphQL API
Configuration Reference
| Field | Required | Default | Description |
|---|---|---|---|
mondayApiToken | Yes | -- | monday.com API token for posting responses |
signingSecret | Yes | -- | HMAC signing secret from custom agent setup |
agentId | No | "main" | Which OpenClaw agent handles monday.com messages |
mondayApiUrl | No | "https://api.monday.com/2" | monday.com API endpoint (override for staging/dev) |
Environment Variables
| Variable | Default | Description |
|---|---|---|
OPENCLAW_GATEWAY_URL | http://127.0.0.1:18789 | Internal gateway URL for agent routing |
OPENCLAW_GATEWAY_TOKEN | -- | Gateway auth token (if different from plugin context) |