Pasting long-lived tokens into random forms is how teams leak credentials and misconfigure phone number IDs. Embedded Signup is Meta’s guided path: you authenticate with Facebook/Meta, select or create the right business assets, and the platform exchanges codes securely behind the scenes.
Pyngdesk supports Connect with WhatsApp (Embedded Signup) on WhatsApp setup (/whatsapp/onboarding). This walkthrough covers what to prepare, what you will see, and how to fix common failures.
What Embedded Signup is
Embedded Signup uses Meta’s JS SDK inside your product flow. You:
- Click Connect with WhatsApp in Pyngdesk
- Complete Meta’s popup / flow (business, WABA, phone number permissions)
- Pyngdesk receives a code/token exchange on the backend
- Your organisation stores the integration (WABA ID, phone number ID, encrypted access token, status)
Manual credential paste may exist as a fallback for special cases — prefer Embedded Signup whenever possible.
Before you start (prep checklist)
- Access to the Facebook/Meta account that can manage the Business Manager
- Permission to create or select a WhatsApp Business Account
- A phone number ready for API use
- If the number is on WhatsApp Business App / consumer WhatsApp, plan to disconnect it first and wait a few minutes
- Business verification status understood (unverified businesses face limits)
- You are logged into Pyngdesk as an organisation admin
Step-by-step in Pyngdesk
1. Open WhatsApp setup
Go to WhatsApp setup (/whatsapp/onboarding) from settings / organisation navigation.
2. Start Embedded Signup
Choose Connect with WhatsApp. Allow pop-ups for the Meta domain.
3. Authenticate and select assets
In Meta’s flow, pick the correct Business portfolio, WABA, and phone number. Double-check you are not linking a personal test asset by mistake.
4. Return to Pyngdesk
When the flow completes, you should see a connected state: display phone number, verified name (when available), integration status, and ideally quality rating.
5. Verify webhooks and messaging path
Send a test inbound message from a personal phone to the business number and confirm it appears in Chats (/chats). If inbound fails, check webhook configuration with your technical admin (Meta App Dashboard subscriptions, including messages and template status updates).
6. Create a first utility template
Open Templates (/templates) and submit a simple utility template so outbound paths are ready.
Number migration tips
- You generally cannot keep the same number active on the regular app and the Cloud API simultaneously
- Export important Business App chat history if you need it offline — API history starts fresh in your platform inbox
- Tell customers nothing about “new WhatsApp” — the number stays the same when migration is clean
- Avoid migrating minutes before a mega campaign; leave buffer for verification issues
Common failures and fixes
| Symptom | Likely cause | What to try |
|---|---|---|
| Popup blocked | Browser pop-up blocker | Allow pop-ups; retry |
| Flow closes with error | Wrong Meta user / missing permissions | Switch to Business admin user |
| Number unavailable | Still registered on WhatsApp app | Delete/disconnect app registration; wait; retry |
| Connected but no inbound | Webhook / app subscription gaps | Verify Meta webhook URL and fields |
| Status error | Token or asset mismatch | Re-run Embedded Signup as admin; contact support with org ID |
| Quality missing / unexpected | New number or Meta delay | Refresh later; send careful tests only |
Never paste tokens into chat with freelancers. Admins only.
What “good” looks like after connect
- Integration status active
- Correct display number
- Team can open Chats and see a test message
- At least one Approved template (optional but recommended)
- Members invited without sharing Meta passwords
- Quality Green or you are deliberately warming a new number slowly
Security notes
- Embedded Signup reduces token handling errors but does not remove the need for least-privilege Meta roles
- Keep Pyngdesk admin seats limited
- Offboard staff in Organisation → Members, not by silence
- Review connected assets quarterly
Frequently Asked Questions
Do I need a developer?
For standard Pyngdesk Embedded Signup, no. Developers help if you maintain custom Meta apps or webhooks outside the product.
Can I connect multiple numbers?
Product behaviour depends on your organisation’s integration model (typically one active WhatsApp integration per organisation). Confirm in-product if you need multi-number setups.
Is Embedded Signup the same as the green App?
No. You are connecting the Business Platform / Cloud API, not installing the consumer Business App.
