Fix [400] [133010] Account not registered in Make WhatsApp Business Cloud: run Register a Sender once with a 6-digit PIN, plus 133016, 133005 and 133006.
Updated 15 Oct 2026 · ~6 min read
Disclosure: this guide has one affiliate link to Make, marked "affiliate link", and mentions our Fiverr fix service. Error messages, settings and limits come from Make Help Center / app docs, Meta WhatsApp Cloud API docs and Make Community thread 105136 checked on 15 October 2026; anything we could not confirm is flagged for review before publishing. We did not reproduce these in a live Make scenario for this guide. Prices, where mentioned, are as seen from the US.
Short answer: [400] [133010] (#133010) Account not registered means the phone number is known to Meta but has not been registered for the WhatsApp Cloud API, so it can't send yet. In Make, add WhatsApp Business Cloud › Register a Sender, pick the same connection and phone number, enter a 6-digit PIN, run it once, then delete the module and retry.
Everything here works on Make's Free plan. The steps come from Make's WhatsApp Business Cloud troubleshooting page and Meta's Cloud API docs; we did not register a number ourselves for this guide.
What 133010 means
Meta's Cloud API error code list gives 133010 as "Phone number not registered on the WhatsApp Business Platform." and the fix as "Register the phone number before trying again." Make's troubleshooting page shows the error as [400] [133010] (#133010) Account not registered and explains that the number "has been added to your Facebook Business Portfolio but hasn't been officially registered as a sender on the WhatsApp Business Platform."
Meta's registration docs say you can only register a number through the API, not in WhatsApp Manager or the App Dashboard. That is why Make has a module for it. The error usually shows up on Send a Template Message or Send a Message, often right after a new connection or a new number.
Fix: register the sender in Make
- In the scenario, add WhatsApp Business Cloud › Register a Sender (you can put it on a new, unconnected spot in the canvas).
- Select the same Connection and the Sender ID (phone number ID) that the failing module uses.
- Enter a 6-digit PIN. If two-step verification is already on for the number, it must be that PIN. If it isn't, the 6 digits you enter become the new two-step verification PIN, so write it down.
- Right-click the module and choose Run this module only, once.
- When it succeeds, delete the Register a Sender module and run the original scenario again.
Don't leave Register a Sender inside the running scenario. Meta limits registration to 10 requests per business number in a 72-hour moving window; after that it returns error 133016 and blocks registration of that number for the next 72 hours.
If Register a Sender fails or 133010 comes back
| You see | What Meta's docs say | What to do |
|---|---|---|
133016 |
Over 10 registration requests in 72 hours | Wait 72 hours; stop any scenario that registers on every run |
133005 |
Two-step verification PIN incorrect | Use the correct PIN. To reset it, Meta says to disable two-step verification, then set a new PIN |
133008 / 133009
|
Too many PIN guesses / PIN entered too quickly | Wait the time given in the error details |
133006 |
Phone number needs to be verified before registering | Verify the number first (Make has Verify a Sender: request a code by SMS or voice, then verify it) |
133015 |
The number was recently deleted and deletion has not finished | Wait 5 minutes, then try again |
Also check the number's status in WhatsApp Manager. A Make Community answer in thread 105136 suggests confirming the number shows as Active there.
Make's two-step verification note
Make's WhatsApp Business Cloud requirements say you must turn off two-step verification for the WhatsApp Business number if it's enabled, and its troubleshooting page has a separate error for certificate creation when two-factor authentication is still on. Meta's registration endpoint, on the other hand, takes the existing PIN if two-step verification is on. If registration fails with a PIN error, follow Make's note: turn two-step verification off in WhatsApp Manager, then register again with a new 6-digit PIN.
After it works
- New chats must start with Send a Template Message; Make's docs say you can use Send a Message only after the customer has replied to a template.
- Until Meta has reviewed your business and display name, Make's docs mention a limit of 5 business-initiated test messages every 24 hours.
- Coexistence numbers (the WhatsApp Business app and Cloud API on one number) have their own connection mode in Make; see Make WhatsApp automation.
Sources checked (15 October 2026)
- Make apps: WhatsApp Business Cloud troubleshooting (Account not registered), WhatsApp Business Cloud (requirements, Register/Verify a Sender)
- Meta for Developers: Cloud API error codes, Register a business phone number (updated 26 Jun 2026)
- Make Community: 105136, 93457
Don't have a Make account yet? You can build and test this scenario on Make's free plan.
Create a free Make account (opens Make in a new tab)
Affiliate link: Flowpaja may earn a commission at no extra cost to you.
FAQ
What does WhatsApp error 133010 mean?
Meta's error list says the phone number is not registered on the WhatsApp Business Platform. The number is in your business portfolio but not registered as a Cloud API sender.
How do I fix 133010 in Make?
Add WhatsApp Business Cloud Register a Sender, select the same connection and phone number, enter a 6-digit PIN, run it once, then delete the module and retry.
How many times can I register a number?
Meta allows 10 registration requests per business number in a 72-hour moving window. After that you get error 133016 and must wait 72 hours.
Which PIN do I use?
If two-step verification is on, the existing PIN. If it is off, the 6 digits you enter become the new PIN. Make's requirements say to turn two-step verification off for Make connections.
Top comments (0)