The platform supports Meta Embedded Signup, which allows users to directly connect their WhatsApp Business accounts through a guided onboarding flow without leaving your application.
This simplifies onboarding and removes the need for manual Meta Business configuration.
What is Embedded Signup
Embedded Signup is a Meta-provided flow that enables users to:
- connect their WhatsApp Business account
- grant required permissions
- complete onboarding within your platform
This flow is powered by Meta (Facebook) and requires proper app configuration and approval.
Why Embedded Signup is Used
Embedded Signup helps:
- reduce onboarding friction for users
- automate WhatsApp Business API connection
- eliminate manual Meta setup steps
- improve conversion for new users
Configuration Requirements
Before using Embedded Signup, you must:
- create a Meta App in the Meta Developer Console
- enable WhatsApp Business Platform API
- configure App ID and App Secret
- generate configuration IDs (with and without catalog)
- set up webhook verification
To use Embedded Signup in production, your Meta app must be verified.
Verification ensures:
- your app is trusted by Meta
- permissions are approved
- users can connect their accounts without restrictions
- Go to: https://developers.facebook.com/
- Click My Apps → Create App
- Select Business App
- Enter:
- Click Create App
Step 2: Add WhatsApp Product
- Inside your app dashboard
- Click Add Product
- Select WhatsApp
- Complete the basic setup
Go to App Settings → Basic
Make sure to add:
- App Name and Logo
- Privacy Policy URL
- Terms of Service URL
- App Domain (your platform domain)
Then go to: Business Settings → Security Center
- Go to Facebook → Configuration
- Generate:
- Configuration ID (with catalog)
- Configuration ID (without catalog)
- Copy:
- Add these values to your platform settings
- Go to Whatsap → Configuration and add the webhook URL provided from platform to recive all incoming whatsapp messages
Step 5: Add Permissions (IMPORTANT)
Go to: App Review → Permissions and Features
Request the following permissions:
business_managementwhatsapp_business_managementwhatsapp_business_messagingcatalog_managementemailpublic_profile
Permission Justification (Copy-Paste Ready)
Use the below explanations when Meta asks for justification:
business_management
Our platform allows businesses to connect and manage their WhatsApp Business accounts. This permission is required to access business-level assets and enable account linking via embedded signup.
whatsapp_business_management
This permission is required to manage WhatsApp Business account settings, phone numbers, and configurations after the user connects their account through our platform.
whatsapp_business_messaging
Our platform enables users to send and receive WhatsApp messages, including automated notifications, campaigns, and customer conversations. This permission is essential for message delivery and communication workflows.
catalog_management
This permission is used for businesses that utilize product catalogs. It allows syncing and managing catalog items for use in WhatsApp commerce features such as product messages and interactive flows.
email
We use this permission to identify the user’s account and ensure proper mapping between their Meta account and our platform.
public_profile
This permission is required to access basic profile information to create and manage user sessions securely within our platform.
Step 6: Complete App Review Sections
Go to: App Review → Settings
Complete all sections:
- Branding
- Audience
- Clients
- Data Access
- Verification
All sections must be completed before submission.
Step 7: Submit Screencast Video
You must upload a video showing:
- Login into your platform
- Starting Embedded Signup
- Connecting WhatsApp account
- Accepting permissions
- Completing onboarding
- Sending or receiving messages
Step 8: Submit for Review
- Go to App Review
- Submit requested permissions
- Wait for Meta approval
Important Notes
- App must be in Live Mode before production use
- Missing permissions = rejection
- Incomplete video = rejection
- Business verification is mandatory
⚠️ Need Help?
Meta verification can be complex and time-consuming.
If you need assistance, you can contact our support team.
We provide verification setup as an add-on service.
Twilio TURN Configuration (WhatsApp Calling)
To enable WhatsApp calling functionality in the platform, a TURN (Traversal Using Relays around NAT) server is required. TURN ensures stable voice connectivity, especially in restricted or NAT-based network environments.
We recommend using Twilio TURN services for reliable performance.
Why TURN is Required
WhatsApp calling relies on WebRTC technology, which may fail in certain network conditions such as:
- firewalls blocking direct connections
- strict NAT environments
- corporate or restricted networks
TURN acts as a relay server to ensure calls are successfully connected even in these scenarios.
How It Works
- Twilio provides TURN credentials (temporary or generated)
- These credentials are used by the platform to establish call connections
- The TURN server relays audio data between users when direct connection fails
Step 1: Create Twilio Account
- Go to: https://www.twilio.com/
- Sign up or log in to your account
- Navigate to Twilio Console Dashboard
- Copy the following: Account SID & Auth Token, these will be used to authenticate TURN requests.
- Add the following details in your platform settings: Twilio Account SID mTwilio Auth Token
- Once added:Click Test TURN
- The platform will automatically generate:
- TURN URL
- TURN Username
- TURN Credential
Meta Webhook Relay allows you to forward incoming WhatsApp (Meta) webhook events to another external endpoint without modifying your primary webhook configuration.
This is useful when you want to duplicate or redirect webhook data to additional systems such as automation tools, CRMs, or custom APIs.
What this does
- receives webhook events from Meta (WhatsApp Cloud API)
- forwards the raw payload to a secondary webhook URL
- preserves original request structure and headers
- enables parallel processing of webhook events
Typical Use Cases
- send WhatsApp events to external automation platforms
- integrate with third-party CRMs or analytics systems
- duplicate webhook data for logging or monitoring
- trigger workflows outside the main platform
How It Works
- Meta sends webhook events to your primary webhook
- The platform captures the event
- If relay is enabled, the same payload is forwarded to your configured URL
- The target system receives the webhook as a standard POST request
Configuration Fields
- Forward URL
The external endpoint where webhook events will be sent
- Verify Token
Used only for webhook verification (not for forwarded events)
- Relay Toggle
Enables or disables webhook forwarding
- Relay Scope
Choose what to forward:
- Messages
- Status updates
- Account updates
Important Notes
⚠️ Credit Consumption Warning
Each forwarded webhook event will consume platform credits.
- Every incoming event = 1 credit used (for forwarding)
- High message volume can increase credit usage significantly
- Monitor usage if relay is enabled in production
Best Practices
- Enable relay only when required
- Filter relay scope to avoid unnecessary events
- Use a reliable external webhook endpoint
- Monitor success/failure logs regularly
Testing
You can validate your setup using:
- Test Verification → checks webhook validation flow
- Send Meta-Style Sample → sends a sample payload to your endpoint
When to Use
Use Meta Webhook Relay when:
- you need multi-system integrations
- you want to extend platform functionality externally
- you are building advanced automation pipelines
Support
⚠️ If webhook forwarding is not working, verify your endpoint response and ensure it accepts POST requests properly.
Last modified on April 24, 2026
