Dynamically register whats app business number through App

Questions
1

Describe the problem/error/question

I have a use case where Users will download the app and enter their whats app Business number, which they want to register for Automation. Using the Meta example by hardcoding test phone Number I am able to complete the automation.
Where I am stuck is, in real use case how does a user register to this automation service?. I want my app to call Meta API to register the number for the automation process. Any inputs DO’s DONT’s will be helpful.

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

@manju_reddy you can use Meta’s “Embedded Signup” flow to enable users to connect their WhatsApp Business accounts with your app:

User Flow:

  • User clicks “Connect WhatsApp” in your app.

  • User is redirected to Meta’s OAuth flow.

  • User logs in to their Facebook Business Manager.

  • User selects their WhatsApp Business Account and phone number.

  • User grants permission to your app.

  • Meta returns access tokens to your app.
    What you get:

  • WhatsApp Business Account ID (WABA ID).

  • Phone Number ID.

  • Access token for the specific user’s number.

  • Permission to send messages on their behalf.
    Implementation:

  • Register your app in Meta’s Developer Portal.

  • Request “WhatsApp Business Management” permissions.

  • Implement the “Embedded Signup” flow.

  • Store the user’s WABA ID, Phone Number ID, and tokens in your database.

  • Use these credentials in your n8n workflows per user.

Does this help!

3

Hi @manju_reddy, welcome to the n8n community!
One idea could be that instead of trying to register the number purely via API, you position your app as an official SaaS platform and use Meta’s Embedded Signup as part of your activation flow. In that case, you’re not directly controlling the registration itself, but rather orchestrating the entire process before and after it, making the experience seamless for the user while still staying fully within Meta’s rules.

4

Just a heads up, n8n’s built-in WhatsApp node only handles messaging (sending/receiving), it doesn’t support the registration or onboarding side of things at all. So for the actual number registration you’d be using HTTP Request nodes to call Meta’s Graph API directly — specifically the POST /{PHONE_NUMBER_ID}/register endpoint after the number is added to a WABA through Embedded Signup. Also worth looking into Meta’s Tech Provider program since you’re essentially building a multi-tenant setup where multiple users bring their own numbers, that program is specifically designed for ISVs managing multiple customer WABAs and it’ll save you a lot of headaches down the road with webhook routing and access token management.