Module Architecture

flowchart TD
    SUBSMOD["sadeem_subscription\nSubscription Base"]

    CFG["sadeem.waha.config\nWAHA server config\nAPI URL · API key · engine · webhooks"]
    LINE["sadeem.waha.config.line\nsubscription WhatsApp line\nsession name · status · phone"]
    SUB["sadeem.subscription (inherit)\nlinks to WAHA config lines\nadd WhatsApp access"]

    SUBSMOD --> SUB
    CFG --> LINE
    LINE --> SUB

    CFG --> A1([action_test_connection\nGET /health on WAHA server])
    CFG --> A2([action_view_lines\nopen subscription lines for this config])

    LINE --> A3([action_provision\ncreate WAHA session on slave instance])
    LINE --> A4([action_refresh_status\nsync session status from slave])
    LINE --> A5([action_stop_session\nstop WhatsApp session on slave])
    LINE --> A6([action_disable\nmark line as disabled])
    LINE --> A7([action_activate\nmark line as active])
    LINE --> A8([_compute_session_name\nderive session name from subscription domain])
    LINE --> A9([_get_slave_url\nresolve slave base URL from subscription domain])
    LINE --> A10([_build_webhook_url\nconstruct WAHA webhook URL pointing to slave])

    SLAVE[/Slave Odoo Instance\nWAHA module installed on slave/]
    WAHA[/WAHA API Server\nWhatsApp session management/]

    A3 --> SLAVE
    A4 --> SLAVE
    A5 --> SLAVE
    SLAVE --> WAHA

Module Description

SAAS Subscription WhatsApp (WAHA) integrates the WAHA (WhatsApp HTTP API) service into the Sadeem SAAS platform.

Dependencies

• sadeem_subscription

Menus

SAAS Management
└─ Infrastructure
    └─ WhatsApp (WAHA)
        ├─ WAHA Configurations
        └─ Subscription Lines

Session Lifecycle

Draft → Active (provision session on slave)
           ↓
        scan_qr_code (customer scans QR)
           ↓
        working (connected)
           ↓
     Expired / Disabled

Architecture Notes

• The master (this module) stores WAHA server credentials and calls the slave instance's provisioning endpoint — it never calls the WAHA API directly.
• The slave's sadeem_waha_whatsapp_saas module handles the actual WAHA communication.
• Session names are derived from the subscription domain (dots replaced with underscores): e.g. client.sadeem.cloud → client_sadeem_cloud.
• One WAHA config can be marked as default per company for automatic assignment.

Key Fields

WAHA Configuration (sadeem.waha.config)

WAHA Config Line (sadeem.waha.config.line)

Subscription — WAHA additions (sadeem.subscription inherit)

Key Actions

Warnings & Important Notes

• One default per company: @api.constrains raises UserError if more than one WAHA config is marked as is_default per company.
• Overlap prevention: @api.constrains raises UserError if a subscription already has an active or draft WAHA line when adding a new one (one active line per subscription at a time).
• Subscription domain required: action_provision raises UserError if the linked subscription has no domain set (session name cannot be computed).
• Session name format: Dots in the domain are replaced with underscores, e.g., client.sadeem.cloud → client_sadeem_cloud.
• Slave module check: Before provisioning, action_provision checks that sadeem_waha_whatsapp_saas is installed on the slave; installs it if not, or raises UserError if unreachable.
• Slave communication errors: All slave API calls raise UserError with HTTP status or exception details on failure.
• SQL constraint: _sql_constraints on sadeem.waha.config.line enforces uniqueness of session names per WAHA config.
• No direct WAHA API calls: The master never calls WAHA directly — all WAHA operations go through the slave Odoo instance.