Your business
Authorised Meta administrator
Guided WhatsApp Business Platform onboarding
Connect WhatsApp Cloud API with Meta Embedded Signup
Start the official connection flow in a few clicks. BotLinkd guides your business through Meta asset selection, phone-number authorisation, permissions and the standard Cloud API connection without requiring a custom implementation.
- Meta Embedded Signup
- No manual token copying
- Standard webhook connection
BotLinkd is an independent business messaging platform and is not owned or operated by Meta.
Guided connection flow
From business authorisation to an active workspace
Business and WhatsApp assets
WABA, number and permissions
BotLinkd workspace
Inbox, automation and integrations
Standard onboarding is designed for no-code connection. Custom development remains available when your business needs specialised API or system workflows.
Official Meta Tech Partner
Built around the official WhatsApp Business Platform
1,300+ clients served
Business messaging onboarding and operations
Policy-aware platform
Controls designed for responsible business messaging
Onboarding support
Help with eligibility, assets and connection steps
Direct answer
How do you connect WhatsApp Cloud API to BotLinkd?
Open Connect with Meta in BotLinkd, sign in with an authorised Facebook account, choose or create the relevant business and WhatsApp assets, select an eligible phone number and approve the requested permissions. BotLinkd then connects supported Cloud API messaging and webhook events to your workspace.
The guided flow removes the normal need to copy access tokens, create a webhook endpoint or build a customer inbox before the number can be used in BotLinkd.
Product walkthrough
Watch the Meta Embedded Signup flow
See where to begin the connection, choose the applicable business assets and authorise BotLinkd for the supported WhatsApp Business Platform workflow.
What the walkthrough demonstrates
- Where the Embedded Signup connection starts in BotLinkd
- How authorised Meta business and WhatsApp assets are selected
- How the requested permissions are reviewed and approved
- What to check after the connection returns to BotLinkd
The screens and available options can differ according to Meta account status, country, existing assets and product updates.
Prepare before onboarding
What you need before you connect
Preparing these items first reduces failed sign-ins, missing-asset problems and avoidable delays during the connection flow.
Authorised Meta access
Use a Facebook account that has the required administrator access to the relevant Meta business portfolio and WhatsApp assets.
Business information
Keep the legal business details and website information used for Meta business onboarding available and accurate.
An eligible phone number
Use a number that can receive the required verification method. Existing WhatsApp Business app numbers may need a coexistence or migration check.
A clear messaging use case
Know how your business will use WhatsApp, who will receive messages and how customer permission and opt-outs will be managed.
Do not delete or re-register an active WhatsApp Business app number before its current coexistence or migration eligibility has been checked.
Ask BotLinkd to check the numberConnection process
Four steps from sign-in to a configured workspace
The visible business authorisation happens inside Meta Embedded Signup. BotLinkd then uses the approved connection for supported messaging and platform events.
-
Open Connect with Meta
Create or sign in to your BotLinkd account, open the WhatsApp platform setup area and start the Meta Embedded Signup flow.
The Meta sign-in and authorisation screens are presented within the guided onboarding flow. -
Select the business and WhatsApp assets
Choose or create the applicable Meta business portfolio, WhatsApp Business Account and eligible phone number.
The options available depend on your account permissions, existing assets and Meta eligibility. -
Authorise the connection
Review and approve the requested permissions so BotLinkd can connect supported messaging, status and webhook events.
Standard onboarding avoids manually copying access tokens or configuring webhook endpoints yourself. -
Verify and configure the workspace
Complete any required phone verification, confirm the connected number and configure agents, templates, automations and integrations.
Verification and review timing can vary according to the number, business assets and Meta account requirements.
Implementation options
Guided onboarding compared with a custom Cloud API build
Both options use official WhatsApp Business Platform infrastructure. The main difference is whether your team builds and maintains the business application layer or uses BotLinkd.
| Area | Custom implementation | BotLinkd guided onboarding |
|---|---|---|
| Business authorisation | The implementation team must coordinate account access, business assets and platform permissions across separate setup steps. | Meta Embedded Signup presents the applicable business and WhatsApp asset choices in one guided flow. |
| Access credentials | Developers may need to create, store and rotate access credentials as part of a custom implementation. | BotLinkd manages the standard connection workflow so customers do not need to copy access tokens into the dashboard. |
| Webhook setup | A custom application must expose, verify and maintain its own webhook endpoint and event handling. | Supported message and status events are connected to the BotLinkd platform during standard onboarding. |
| Business workspace | A custom interface, user controls, inbox and reporting layer must be designed and maintained separately. | The connected number can use BotLinkd inbox, automation, campaigns, analytics, APIs and integrations according to the selected plan. |
| Technical effort | A custom build usually requires development, testing, hosting, monitoring and ongoing maintenance. | The standard BotLinkd connection is designed for no-code onboarding, while developers remain optional for custom integrations. |
After the connection
Turn the connected number into a complete business messaging workspace
BotLinkd is not only a connection utility or AI chatbot. It provides the operational tools teams need to manage customer communication over the official WhatsApp Business Platform.
Two-way customer chat
Receive customer messages and manage supported replies from the BotLinkd business messaging workspace.
Explore customer chatMulti-agent shared inbox
Give authorised sales, support and operations users access to one connected customer conversation workspace.
View Cloud API platformAI with human control
Use optional AI assistance with conversation memory, human handover, per-contact AI pause and platform-wide AI pause.
Explore AI assistanceTemplates and campaigns
Create approved templates, organise opted-in audiences, schedule messages and review available delivery events.
Explore campaignsAutomation and auto-replies
Configure supported routing, auto-replies and operational workflows for repetitive customer communication.
Browse platform servicesAPIs, webhooks and integrations
Connect websites, CRMs, e-commerce stores and internal systems using BotLinkd APIs, webhooks and supported integrations.
View integrationsSecurity and control
Business-authorised access with human control
The connection starts with an authorised Meta administrator. After setup, BotLinkd lets businesses control agents, workflows and optional AI behavior within the platform.
- Authorised team access instead of a shared personal device
- Human agent handover for supported conversations
- Per-contact and platform-wide AI pause controls
- API keys and webhooks for controlled system integrations
Frequently asked questions
WhatsApp Cloud API connection questions
Direct answers about timing, developers, existing numbers, platform operation and compliance responsibilities.
How quickly can I connect WhatsApp Cloud API with BotLinkd?
The guided flow can be started in a few clicks, but total completion time is not guaranteed. It depends on administrator access, business assets, phone-number eligibility, verification requirements and any Meta account review.
Do I need a developer to connect my WhatsApp Business number?
A developer is not normally required for the standard BotLinkd onboarding flow. Development may still be useful when your business needs custom API, webhook, CRM, e-commerce or internal-system workflows.
What is Meta Embedded Signup?
Meta Embedded Signup is an official onboarding flow that lets an authorised business select or create the relevant Meta and WhatsApp assets, choose an eligible phone number and grant the permissions required by a technology provider.
Can I connect a number that already uses the WhatsApp Business app?
Possibly. Eligible businesses and numbers may support an official coexistence path. Where coexistence is unavailable or unsuitable, a migration may be required. Do not delete or re-register an active number until the correct path has been confirmed.
Does BotLinkd use WhatsApp Web or QR-code browser automation?
No. BotLinkd connects through the official WhatsApp Business Platform Cloud API operating model, using authorised business assets, permissions and webhooks rather than a mirrored WhatsApp Web session.
What can I use after the number is connected?
Depending on the active BotLinkd plan and account configuration, businesses can use two-way chat, a multi-agent inbox, AI assistance, human handover, automation, templates, broadcast campaigns, scheduled messaging, contact management, analytics, APIs, webhooks and integrations.
Does connecting through BotLinkd ensure account approval or eliminate restriction risk?
No. Meta controls account reviews, template decisions and policy enforcement. Each business remains responsible for lawful messaging, recipient permission, opt-out handling, content quality and compliance with current WhatsApp and Meta policies.
Ready to connect?
Start your official WhatsApp Cloud API onboarding
Create a BotLinkd account to begin the guided connection, or contact the onboarding team first when you need help with an existing number, Meta assets or eligibility.