whatsapp-number-onboarding
Connect WhatsApp Business Numbers to Cloud API
WhatsApp onboarding can fail even when Meta shows a connected number. This skill provides ordered setup checks and troubleshooting guidance for registration, webhooks, and delivery.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "whatsapp-number-onboarding" from https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding.md and its manifest at https://skillstore.io/api/skills/rabbitdesigns22-whatsapp-number-onboarding/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "whatsapp-number-onboarding". The number shows connected, but my webhook receives nothing.
Expected outcome:
- Confirm the number's platform and status directly in Meta.
- Inspect the configured callback URL, messages field subscription, and WABA app subscription.
- Check app and WABA ownership; the same-portfolio recommendation is a field observation.
- Send a controlled test message and inspect webhook delivery before changing account settings.
Using "whatsapp-number-onboarding". Registration returned error 133016 after repeated activation attempts.
Expected outcome:
- Stop registration and deregistration retries.
- The skill associates this error with registration rate limits and a 72-hour block.
- Check Meta's current registration documentation and returned details before scheduling another attempt.
- Do not delete or move the number as a routine retry strategy.
Using "whatsapp-number-onboarding". Templates fail with error 131042.
Expected outcome:
- Inspect Meta's returned error details instead of assuming a cause.
- Review the WhatsApp account's payment method, credit line, timezone, currency, and suspension status.
- Compare delivered and failed messages during the same period before describing the issue as account-wide.
Security Audit
Medium RiskAll 46 static matches are false positives involving Markdown, documentation links, configuration descriptions, and authorized account checks. No evidence found of prompt injection, credential exfiltration, or host reconnaissance. Two semantic risks remain: account deletion without explicit consent safeguards and placing client assets in an agency portfolio to avoid onboarding blocks.
Confirmed security concerns (2)
Risk Factors
โ๏ธ External commands (34)
๐ Network access (5)
๐ Env variables (4)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/rabbitdesigns22-whatsapp-number-onboarding/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/rabbitdesigns22-whatsapp-number-onboarding.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
rabbitdesigns22. (2026). whatsapp-number-onboarding security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding/audits/1BibTeX citation
@techreport{rabbitdesigns22-rabbitdesigns22-whatsapp-number-onboarding-2026,
author = {rabbitdesigns22},
title = {whatsapp-number-onboarding security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "whatsapp-number-onboarding security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "rabbitdesigns22"
date-released: "2026-11-11"
url: "https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding/audits/1"
identifiers:
- type: other
value: "skillstore:rabbitdesigns22-whatsapp-number-onboarding:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Prepare a first business number
Organize required business information, account identifiers, registration steps, and final delivery checks before launch.
Separate client integrations
Review app ownership, hosting projects, webhook destinations, and account identifiers to prevent cross-client configuration mistakes.
Diagnose missing or duplicate messages
Compare number status, app subscriptions, callback domains, and error details before making disruptive changes.
Try These Prompts
Prepare a WhatsApp Cloud API onboarding checklist for my business. List required information and human actions. Do not request tokens or PINs in chat.
Meta shows my number as connected, but incoming messages do not reach my bot. Suggest read-only checks first and distinguish field observations from official guidance.
Our WhatsApp bot stopped receiving messages after a hosting domain change. Review callback URLs, subscribed fields, app subscriptions, and project identity before proposing changes.
Audit our client onboarding plan for ownership, project isolation, token handling, registration limits, and delivery checks. Require approval before deletion, subscription removal, or portfolio changes.
Best Practices
- Confirm account ownership and the exact hosting project before changing identifiers or webhook settings.
- Keep tokens and PINs out of chat; use secure storage and human entry for sensitive values.
- Start with read-only checks and verify current Meta guidance; obtain owner approval before destructive or ownership-changing actions.
Avoid
- Treating a valid token or a green dashboard as proof that messages reach the bot.
- Repeatedly registering or deregistering a number while ignoring rate limits and returned error details.
- Deleting accounts or placing client assets in an agency portfolio without informed approval and a continuity plan.
Frequently Asked Questions
Does this skill connect the number automatically?
Which AI tools are supported?
Does a connected dashboard status prove delivery works?
Are all troubleshooting recommendations official Meta policy?
Should I delete an existing WhatsApp account immediately?
Should client assets use my agency's portfolio?
Developer Details
Author
rabbitdesigns22License
Unknown
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
f38ac41a6255e57978dd6f276aec539d5e9b5255
Maintenance freshness
11/12/2026
Usage
0 downloads ยท 0 views
File structure
๐ SKILL.md