# Connecting your WhatsApp Business Account This guide explains how a Wavy workspace owner connects their own verified WhatsApp Business Account using Meta's Embedded Signup flow. It also clarifies what a partially successful connection looks like if the webhook subscription step does not complete. _Takes about 10 minutes._ ## Before you start > **Before you start** > > You need a Meta Business Account and a phone number that is not already registered on the WhatsApp Business Cloud API. ## 1. What you need before you start Before you begin the connection, ensure you have access to a Meta Business Account where you can add your company. You also need a phone number that is able to receive a one-time verification code and is not already registered to the WhatsApp Business Cloud API on another platform or instance. ## 2. Start the connection from your channels page Navigate to the channels section of your Wavy workspace and look for the option to connect WhatsApp. The system checks the deployment-level configuration to determine if the connect button should be displayed. If the page shows a message that configuration is required instead of a button, this indicates that the underlying setup is pending on Automix's side and is not a setting you can configure as a workspace owner. ## 3. Pick your business account and number in Meta's dialog Once you trigger the connection, a popup window from Meta opens in your browser. Use this dialog to select your Business Account, choose the specific WhatsApp Business Account you want to link, and pick the phone number you are connecting. After you approve the requested permissions, Meta provides your browser with a short-lived authorization code, which is used to secure the handoff without exposing any long-lived credentials. ## 4. What happens after you approve the connection After you approve the connection in Meta's dialog, Wavy uses the authorization code on its servers to exchange it for a business access token. This token remains on Automix's infrastructure and never appears in your browser. The system then uses this token to subscribe your WhatsApp Business Account to the necessary webhooks and registers your phone number for use with the Cloud API. ## 5. If the connection only partly succeeds It is possible for the connection to complete the token exchange and create your channel but fail to subscribe to webhooks. In this scenario, the channel will exist and can send outgoing messages, but it will not be able to receive incoming messages until the connection is re-established. Wavy is designed to report this status plainly to you rather than silently failing or rolling back the entire process. > **Partial connection** > > If webhook subscription fails, your channel will still be created and can send, but will not receive incoming messages until reconnected. This is reported to you plainly rather than rolled back or hidden. ## 6. The Meta app credentials behind this flow This connection process relies on a Meta app that has been registered by Automix at the deployment level. You do not need to provide or manage these credentials yourself; they are managed automatically by the platform. They are listed here for technical transparency so you can understand the components that enable the connect button to function correctly in your workspace. Environment variables: `META_APP_ID`, `META_APP_SECRET`, `META_SIGNUP_CONFIG_ID`, `META_API_VERSION` ## Next - [Wavy documentation](/docs/wavy) - [Template approval basics](/docs/wavy/guides/template-approval-basics) --- Status: reviewed · reviewed by gemini-3.8-flash Author: qwen3.8-27b