Need help setting up a Talk Bot in Nextcloud 32 (Webhook / n8n Integration on Synology RS1221+ with Reverse Proxy)

ℹ️ Support
, , , ,
1

Hi everyone :waving_hand:

I’m trying to set up a Talk Bot in Nextcloud 32 that sends automated messages to Talk chats via n8n.
The bot was successfully created and activated using OCC commands, but every attempt to send messages via the API fails with either
401 (unauthorized) or 400 (value too great for base) errors.

Goal:
The bot should automatically post messages into a specific Talk room (e.g. for status updates or workflow notifications) from n8n.

:gear: Environment

Synology RS1221+

Reverse Proxy: configured via Synology DSM → Application Portal → Reverse Proxy (HTTPS → Nextcloud VM)

Nextcloud: running on a virtual machine (VM) under DSM Virtual Machine Manager

n8n: running in a Docker container on the same Synology

Both services communicate through the internal reverse proxy
(https://cloud.example.net and https://n8n.example.net)

:toolbox: Steps taken so far

Created the bot

occ talk:bot:install “n8nBot” “” “https://n8n.example.net/webhook” “TestBot”

Activated

occ talk:bot:state 1

Added it to the room

occ talk:bot:setup <ROOM_TOKEN>

Tested via curl:

POST /ocs/v2.php/apps/spreed/api/v1/bot/<ROOM_TOKEN>/message

with headers

OCS-APIRequest: true
X-Nextcloud-Talk-Bot-Random:
X-Nextcloud-Talk-Bot-Signature: <HMAC_SHA256(random+body,secret)>

Body:

{ “message”: “Hello from the Bot” }

The signature is generated in n8n using the Crypto node (HMAC-SHA256, hex-encoded).
The random string is a 64-character Base64 value without newlines or “=”.

Despite that, requests always return either 401 or 400,
so I suspect that the stricter API validation in NC 32 or the reverse proxy might alter headers.

:red_question_mark: Questions

  1. Has anyone successfully connected the Talk Bot with Nextcloud 32 / Talk v18?

  2. Are there new requirements for X-Nextcloud-Talk-Bot-Random or the signature format?

  3. Is the endpoint

/ocs/v2.php/apps/spreed/api/v1/bot/<ROOM_TOKEN>/message

still valid, or did it change in recent versions?

  1. Do I need to adjust anything in the Synology reverse proxy (e.g., header forwarding for OCS-APIRequest)?

  2. Does anyone have a working curl or n8n example for NC 32?

:receipt: System info

Nextcloud 32.0.x (Talk App v18.x)

n8n (latest Docker image on Synology)

Nextcloud VM under DSM Virtual Machine Manager

Reverse Proxy configured in DSM (HTTPS → VM)

Full shell and log access available

Thanks in advance for any hints, examples, or working configurations :folded_hands: