Social Media Channels¶

Nexivo supports the following social media channels via dedicated adapters:

Platform	Access Method
WhatsApp	WhatsApp Business API
Facebook	Messenger API
Twitter / X	Direct Messages API
Instagram	Messaging API

Each adapter normalises platform-specific message formats into the common interaction object and handles platform-specific constraints (message length limits, media types, delivery receipts).

WhatsApp¶

Architecture¶

WhatsApp messaging is handled via the WhatsApp Business API. The service depends on communication-core for contact resolution.

graph LR
    WA[WhatsApp\nBusiness API] --> Adapter[WhatsApp Adapter]
    Adapter --> CC[communication-core]
    CC --> Redis[(Redis Cache)]
    CC --> DB[(Contact DB)]
    Adapter --> Router[Routing Engine]

Redis Dependency¶

communication-core caches contact lookups via @Cacheable on ContactService.findContactById. Redis must be available and correctly authenticated for this cache to work.

Common Issue — NOAUTH Redis Errors

If the WhatsApp service logs NOAUTH Authentication required, the Redis password in the Kubernetes secret is missing or incorrect.

Fix: Check the Redis secret in the relevant namespace:

kubectl get secret redis-secret -n <namespace> -o yaml

Ensure REDIS_PASSWORD matches the password configured on the Redis instance. Update the secret and restart the communication-core pod.

Message Types Supported¶

Type	Inbound	Outbound
Text	Yes	Yes
Image	Yes	Yes
Document	Yes	Yes
Audio	Yes	Yes
Template	—	Yes

Configuration¶

TO DO

Document WhatsApp Business Account setup, webhook URL registration, phone number verification, and template approval process.

Facebook Messenger¶

TO DO

Document Facebook Page linking, Messenger webhook configuration, and supported message types.

Twitter / X¶

TO DO

Document Twitter app credentials, DM webhook setup, and rate limit handling.

Instagram¶

TO DO

Document Instagram Business Account linking and Messaging API configuration.