Tentacles Stage 2 Intake

Purpose

This document records the actual running shape of the first Tentacles intake path.

Live Path

1. WAHA on cbr-sh-waha01 receives the WhatsApp event.
2. WAHA posts the event to:
3. http://10.0.0.55:5678/webhook/tentacles/waha-inbound
4. n8n normalizes the payload and filters out non-customer traffic.
5. n8n posts a review item to the local queue API on:
6. http://10.0.0.55:8081/queue
7. n8n sends the holding reply back through WAHA.

Running Components

• cbr-sh-waha01
• 10.0.0.58:3000
• temporary QR-based WhatsApp adapter
• cbr-sh-n8n01
• 10.0.0.55:5678
• intake workflow host
• cbr-sh-n8n01
• 10.0.0.55:8081
• local queue API for operator review items

Dashboards And APIs

n8n

• full web UI
• URL:
• http://10.0.0.55:5678

WAHA

• Swagger/API dashboard
• URL:
• http://10.0.0.58:3000

local queue API

• API only
• root path returns {"error":"not_found"}
• valid endpoints:
• http://10.0.0.55:8081/health
• http://10.0.0.55:8081/queue

Qdrant

• API only in the current deployment
• endpoint:
• http://10.0.0.54:6333

PostgreSQL

• no web UI
• database service only
• endpoint:
• 10.0.0.53:5432

Dify

• container exists
• software not deployed yet
• no UI yet

Langfuse

• container exists
• software not deployed yet
• no UI yet

Current Queue Model

The first operator queue is intentionally simple:

• local queue API on cbr-sh-n8n01
• local SQLite persistence
• pending review items available from:
• GET http://10.0.0.55:8081/queue

This is a prototype-speed choice, not the final architecture.

Proven State

Confirmed with synthetic inbound webhook tests:

• webhook accepted
• n8n execution completed successfully
• operator review items were created
• holding reply calls were accepted by WAHA

Remaining Stage 2 Work

• prove the same path with a real inbound WhatsApp message
• choose and wire the email/operator notification path
• define the first active TV Mount Australia knowledge source
• decide whether queue persistence should move to PostgreSQL before Stage 3