Struct WhatsAppBridge 

pub struct WhatsAppBridge {
    outbound_tx: UnboundedSender<OutboundMsg>,
    health: Arc<Mutex<BridgeHealth>>,
    app_secret: String,
    webhook_verify_token: String,
    target_agent: Option<String>,
    window_state: Arc<Mutex<HashMap<String, u64>>>,
}

Fields

outbound_tx: UnboundedSender<OutboundMsg>

health: Arc<Mutex<BridgeHealth>>

app_secret: String

webhook_verify_token: String

target_agent: Option<String>

window_state: Arc<Mutex<HashMap<String, u64>>>

Per-sender (WhatsApp phone number) last-inbound timestamp (unix ms), for 24h customer service window tracking (spec §3.3). Not persisted to disk in v1 — a restart means the bridge falls back to templates until the next inbound message re-opens the window, an accepted degradation per the spec.

Implementations

impl WhatsAppBridge

pub fn init_global(config: WhatsAppConfig, http: Client)

Initialize the global WhatsApp bridge and start the outbound send background task. No-op if already initialized.

Unlike Discord/Telegram/Slack, there is no inbound connection loop to spawn here — inbound delivery is passive HTTP handled by webhook::handle_verify/handle_inbound, already registered unconditionally on the main axum router (see server/mod.rs) regardless of whether init_global has run. Those handlers return 503 via WhatsAppBridge::get() returning None until this runs.

pub fn get() -> Option<&'static WhatsAppBridge>

pub fn send(&self, msg: OutboundMsg) -> Result<(), String>

Enqueue a message for delivery via the Graph API. Returns error if the bridge task has exited (should not happen in normal operation).

pub fn health(&self) -> BridgeHealth

pub(crate) fn app_secret(&self) -> &str

pub(crate) fn verify_token(&self) -> &str

pub(crate) fn target_agent(&self) -> Option<&String>

pub(crate) fn record_inbound(&self, from_id: &str)

Called by webhook::handle_inbound on each valid inbound message, to update the 24h window state (spec §3.3) and the health snapshot’s last_event_at.

Keys on rest::normalize_phone(from_id), not the raw id, so this matches whatever normalized form rest::send_message looks the number up under — Meta’s inbound from has no + prefix, but a caller sending via handle_whatsapp_send may supply one (E.164); without a shared normalization the window lookup always missed (found via review).

Trait Implementations

impl MessagingBridge for WhatsAppBridge

fn health(&self) -> BridgeHealth

Current connection/health snapshot. Cheap, non-blocking (reads an Arc<Mutex<BridgeHealth>> guarded by a short-lived lock).