Connect WhatsApp Business

For: Company admins and integration owners
Owner: Integration operations
Outcome: Test, monitor, recover, rotate, and disconnect WhatsApp Business safely.
Last verified: 2026-08-30
Next review: 2026-11-28
Status: supported

Connect an approved WhatsApp provider with visible template and webhook health. This guide uses the current supported Sakhaa setup surface and keeps provider-owned approval and availability separate.

Prepare the connection

Provider and Meta approval, template approval, and conversation rules apply.

Confirm the customer-owned business account, number, provider, and consent process.
Complete provider credentials, webhook protection, and template synchronisation.
Use diagnostics or an approved test path. Do not message a customer only for proof.

Connect and prove health

Open /app/whatsapp/settings in the correct workspace.
Save the provider api key, webhook secret, and account identifiers only in the protected setup surface.
Use connection diagnostics and a provider-approved test path. Do not message a customer for proof.
Confirm this healthy result: Connection, webhook, template sync, and operations health are ready.

Use synthetic data and an approved test identity. Do not use customer traffic only to prove a connection.

Monitor and recover

Monitor: Review provider readiness, webhook delivery, templates, sync, credits, and failed messages.
Recover: Repair the failing readiness item, replay only safe inbound work, and avoid duplicate sends.
Rotate: Rotate credentials in a controlled window and rerun connection diagnostics.
Disconnect: Pause automations and outbound work before removing the provider connection.
Limits: Provider and Meta approval, template approval, and conversation rules apply.
Fallback: Pause new outbound work and route approved inbound work to the manual inbox until provider readiness returns.

Support boundary

Sakhaa supports the CRM configuration and product behavior. The provider controls account approval, billing, quotas, and external service availability.

Record the provider, workspace, approximate time, safe error code, expected result, and actual result.
Do not include passwords, access tokens, API secrets, message content, or unnecessary customer data.