Can I add an AI agent to Nextcloud Talk?

Yes. Install the OpenClaw Nextcloud Talk plugin, register the bot on your Nextcloud with a shared secret and webhook URL, and add it to conversations.

Does Nextcloud Talk need to reach my agent?

Yes. Nextcloud delivers messages to a webhook URL, so the agent must be reachable from wherever Nextcloud runs — over a private network if your Nextcloud is internal only.

Why can my Nextcloud Talk bot read but not reply?

The bot registration is missing reply permission. Running a channel status probe reports this explicitly.

← Home

Guide

Connect Nextcloud Talk to Your AI Agent

If your team already runs Nextcloud, Talk is where the conversations are. This puts the agent in there alongside everyone else, on infrastructure you control.

How the Connection Works

Nextcloud Talk bots are registered with the server and receive messages at a webhook URL, authenticated with a shared secret. Two consequences follow.

Your Nextcloud server needs to be able to reach your agent, so the agent needs a URL that is reachable from wherever Nextcloud runs. On an internal-only Nextcloud that means putting both on the same private network.
You need administrator access to your Nextcloud to register the bot. This is not something a normal user account can do.

Install the Plugin

From your instance's Web Terminal:

openclaw plugins install @openclaw/nextcloud-talk

Register the Bot and Configure

Register the bot on the Nextcloud side with a shared secret and the webhook URL your agent will listen on, then add the channel:

openclaw channels add --channel nextcloud-talk \
  --token "<shared-secret>"

The channel accepts nc-talk and nc as aliases if you would rather type less. Once the API user and public webhook URL are set, a status probe will check the bot registration and warn you if it is missing the ability to reply — which is worth running, because a bot that can read but not respond looks identical to a broken one.

Access Control

Direct messages use pairing. An unknown user who messages the bot gets a code, and nothing happens until you approve it:

openclaw pairing list nextcloud-talk
openclaw pairing approve nextcloud-talk <CODE>

Add the bot to the conversations it should take part in. As with most team chat, a bot that is not in a room cannot see it.

Troubleshooting

The bot is registered but never receives anything. Your Nextcloud cannot reach the webhook URL. Test it from the Nextcloud server itself, not from your laptop.
It receives messages but cannot answer. The bot registration lacks reply permission — the status probe calls this out.
Authentication failures. The shared secret does not match on both sides. It is easy to copy with a trailing space.
It ignores a colleague's DM. Their pairing code has not been approved yet.

Need a Hand?

Contact support from your dashboard. We can configure the agent side and help with reachability; registering the bot has to be done by a Nextcloud administrator on your side.