@openclaw/nextcloud-talk) that connects OpenClaw to a self-hosted Nextcloud instance through a Talk webhook bot. Direct messages, rooms, reactions, and markdown messages are supported; media goes out as URLs.
Install
Quick setup (beginner)
- Install the plugin (above).
-
On your Nextcloud server, create a bot:
Keep
--feature response: without it, outbound replies fail with 401. Repair an existing bot with./occ talk:bot:state --feature webhook --feature response --feature reaction <botId> 1. - Enable the bot in the target room settings.
-
Configure OpenClaw:
- Config:
channels.nextcloud-talk.baseUrl+channels.nextcloud-talk.botSecret - Or env:
NEXTCLOUD_TALK_BOT_SECRET(default account only)
--url/--tokenare aliases for the explicit fields;nc-talkandncwork as channel aliases):Equivalent explicit fields:File-backed secret: - Config:
- Restart the gateway (or finish setup).
Notes
- Bots cannot initiate DMs. The user must message the bot first.
- The webhook URL must be reachable from the Nextcloud server; set
webhookPublicUrlwhen the gateway sits behind a proxy. Webhook requests are HMAC-SHA256 signed with the bot secret; invalid signatures are rejected and rate limited. - Media uploads are not supported by the bot API; outbound media is appended as an
Attachment: <url>line. - The webhook payload does not distinguish DMs from rooms; set
apiUser+apiPasswordto enable room-type lookups (cached about 5 minutes). Without them, every conversation is treated as a room. - Outbound requests go through the SSRF guard. For a Nextcloud host on a trusted private/internal network, opt in with
channels.nextcloud-talk.network.dangerouslyAllowPrivateNetwork: true. - With
apiUser/apiPasswordandwebhookPublicUrlset,openclaw channels statusprobes the bot and warns when theresponsefeature is missing.
Access control (DMs)
- Default:
channels.nextcloud-talk.dmPolicy = "pairing". Unknown senders get a pairing code. - Approve via:
openclaw pairing list nextcloud-talkopenclaw pairing approve nextcloud-talk <CODE>
- Public DMs:
channels.nextcloud-talk.dmPolicy="open"pluschannels.nextcloud-talk.allowFrom=["*"]. allowFrommatches Nextcloud user IDs only (lowercased); display names are ignored.
Rooms (groups)
- Default:
channels.nextcloud-talk.groupPolicy = "allowlist"(mention-gated). - Allowlist rooms with
channels.nextcloud-talk.rooms, keyed by room token;"*"sets a wildcard default:
- Per-room keys:
requireMention(default true),enabled(false disables the room),allowFrom(per-room sender allowlist),tools(allow/deny tool overrides),skills(limit loaded skills),systemPrompt. - To allow no rooms, keep the allowlist empty or set
channels.nextcloud-talk.groupPolicy="disabled".
Capabilities
| Feature | Status |
|---|---|
| Direct messages | Supported |
| Rooms | Supported |
| Threads | Not supported |
| Media | URL-only |
| Reactions | Supported |
| Native commands | Not supported |
Configuration reference (Nextcloud Talk)
Full configuration: Configuration Provider options:channels.nextcloud-talk.enabled: enable/disable channel startup.channels.nextcloud-talk.baseUrl: Nextcloud instance URL.channels.nextcloud-talk.botSecret: bot shared secret (string or secret reference).channels.nextcloud-talk.botSecretFile: regular-file secret path. Symlinks are rejected.channels.nextcloud-talk.apiUser: API user for room lookups (DM detection) and the status probe.channels.nextcloud-talk.apiPassword: API/app password for room lookups.channels.nextcloud-talk.apiPasswordFile: API password file path.channels.nextcloud-talk.webhookPort: webhook listener port (default: 8788).channels.nextcloud-talk.webhookHost: webhook host (default: 0.0.0.0).channels.nextcloud-talk.webhookPath: webhook path (default: /nextcloud-talk-webhook).channels.nextcloud-talk.webhookPublicUrl: externally reachable webhook URL.channels.nextcloud-talk.dmPolicy:pairing | allowlist | open | disabled(default: pairing).openrequiresallowFrom=["*"].channels.nextcloud-talk.allowFrom: DM allowlist (user IDs).channels.nextcloud-talk.groupPolicy:allowlist | open | disabled(default: allowlist).channels.nextcloud-talk.groupAllowFrom: room sender allowlist (user IDs); falls back toallowFromwhen unset.channels.nextcloud-talk.rooms: per-room settings and allowlist (see above).- Static sender access groups can be referenced from
allowFromandgroupAllowFromwithaccessGroup:<name>. channels.nextcloud-talk.historyLimit: group history limit (0 disables).channels.nextcloud-talk.dmHistoryLimit: DM history limit (0 disables).channels.nextcloud-talk.dms: per-DM overrides keyed by user ID (historyLimit).channels.nextcloud-talk.textChunkLimit: outbound text chunk size in chars (default: 4000).channels.nextcloud-talk.chunkMode:length(default) ornewlineto split on blank lines (paragraph boundaries) before length chunking.channels.nextcloud-talk.blockStreaming: disable block streaming for this channel.channels.nextcloud-talk.blockStreamingCoalesce: block streaming coalesce tuning.channels.nextcloud-talk.responsePrefix: outbound reply prefix.channels.nextcloud-talk.markdown.tables: markdown table rendering mode (off | bullets | code | block).channels.nextcloud-talk.mediaMaxMb: inbound media cap (MB).channels.nextcloud-talk.network.dangerouslyAllowPrivateNetwork: allow private/internal Nextcloud hosts past the SSRF guard.channels.nextcloud-talk.accounts.<id>: per-account overrides (same keys);defaultAccountpicks the default. Env varsNEXTCLOUD_TALK_BOT_SECRET/NEXTCLOUD_TALK_API_PASSWORDapply to the default account only.
Related
- Channels Overview — all supported channels
- Pairing — DM authentication and pairing flow
- Groups — group chat behavior and mention gating
- Channel Routing — session routing for messages
- Security — access model and hardening