! URGENT Alternative to WhatsApp Business API for Personal Automation with n8n (Resume Bot Use Case)

Questions
1

:red_exclamation_mark: Problem Summary
I was trying to use the WhatsApp Business Cloud API to automate resume intake via WhatsApp using n8n. However, I encountered multiple issues:

1. My WhatsApp Business Account (WABA) was disabled for violating Meta’s Commerce Policy, even though I’m not a business.

2. Both my phone number and test number were showing as unregistered.

3. I received an error:
    The WhatsApp App ID already has a webhook subscription. Delete it or use another App before executing the trigger.
	This made it impossible to activate a new n8n workflow with a WhatsApp trigger.

Ultimately, I learned that using WhatsApp’s official Business API is not viable for personal or non-commercial use.

My Use Case
I’m building an automation in n8n to handle resumes received via WhatsApp.

Candidates send resumes to my personal WhatsApp number.
I wanted to:
Receive these messages via n8n
Upload resumes to Google Drive
Parse and extract candidate info using Document Parser

Why the Official API Doesn’t Work
I don’t have a registered business, and I’m using my personal number.
The WhatsApp Business API requires business verification and adherence to the Commerce Policy.
This use case was flagged as non-compliant, and my WABA was disabled.
Meta rejected the reactivation request since I don’t represent a business.

2

Hi there, yes, your use case is not viable if you’re on a testing mode because testing mode can only be accessed by those with the number that is registered as test users where in your use case, the candidate is a new unknown number, so you need to make the app on like a production mode which needs whatsapp/meta to verify your app and business

i would suggest you to use Gmail instead of whatsapp

so then people that wants to apply to your job list will then sends an email to you that you will check, and do the rest of the workflow that you mentioned above

3

Alternatively, if your flow can only be handled by WhatsApp, you might consider using an unofficial WhatsApp API provider like Evolution, etc., that offers a Webhook feature. This could solve your current issue.

However, you must be aware of the risks associated with using an unofficial API (e.g., account suspension/ban). Based on my experience, simply listening to messages carries less risk, but broadcasting messages significantly increases it.

4

Hi,

Thanks for the response earlier. Fortunately, I was able to submit a review request in time, and Facebook has reversed the action — my WhatsApp Business account is now active again.

I’d appreciate some guidance on the correct step-by-step process to set up and use the WhatsApp Cloud API in a way that avoids any further issues. Specifically:

  • What are the best practices for testing without violating policies?
  • What rules and limitations should I be aware of?
  • How do I properly transition the app from development to production to ensure a smooth experience?

Thanks in advance for the help!

5

Hi, im glad that you can make it active again

and for the step by step
for testing,i would suggest these:

  • use a test number or connet your business wa number to be the sender
  • add test numbers that you know and have control or consent from the phone number owner to be the test user to send message to
  • the conversation always needs to start and initiated by the user, not you
  • avoid sending bulk messages

for your case, if you follow the tips that i mentioned above, you should be great

and for transitioning to prod, i would say:

  • verify your business, which i think you alredy did
  • if you’re still using a test number, now add a real one and connect it as the sender
  • and for the test users, remove all of them
  • enable 2fa for extra security
  • NEVER hardcode any credentials, like your api key or app id or app secret

and as always DYOR, but this tips should point you to the right direction to make your own research

if this helps please give it a like and mark it as the solution, thank you!