Messaging & integrations

Meta WhatsApp Cloud API: fields and setup

Find the CRM settings, identify the credentials and understand the webhook prerequisite.

Guide for clients · Rapivexa 1.0.4 · Reviewed 6 October 2026

Rapivexa whatsapp settings screen from a sample clinic — Actual local CRM screen using a sample clinic. Click to enlarge. Provider connection is not implied.

Step by step

As clinic admin, open Communication → WhatsApp inbox. Expand WhatsApp API & template settings below the inbox.
In your Meta developer account, open the WhatsApp product setup for your business app. Obtain the Phone number ID and an access token suitable for your production account. The phone number ID is not your phone number or WhatsApp Business Account ID.
Enter Phone number ID, supported Graph API version, Access token and App secret in the CRM settings. Choose a webhook verify token privately; do not publish any of these secrets.
Ask AlphaRapid for a verified public webhook URL for your clinic before registering a callback with Meta. The current Node runtime does not expose the legacy WhatsApp PHP webhook publicly; the old displayed path is not a working setup instruction.
Create and obtain approval for the required message templates in your WhatsApp management account. Match each CRM event template name and language code to the approved template.
Save settings, then have AlphaRapid verify an outgoing test, an incoming message and delivery status. Enable routine outgoing messages only after the complete connection is verified.

Keep in mind

Current availability: settings are accessible, but end-to-end webhook delivery is not verified in the Node runtime. Filling fields alone does not activate a working integration. Blank saved secret fields retain existing values; never share screenshots containing tokens. Meta account menus and supported API versions may change.

Official provider references

Reviewed 6 October 2026. Meta developer documentation may require sign-in; external menu names can change. External Meta account screenshots are not reproduced here.