Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API
Join our community

Actions148

Overview

This node integrates with the Wassenger WhatsApp API to perform various operations related to WhatsApp messaging and management. Specifically, for the "Other" resource with the "Verify number exists" operation, it allows users to check if a given phone number (in international E.164 format) is registered on WhatsApp. This can be useful in scenarios such as validating contacts before sending messages, cleaning contact lists, or verifying user registration status.

Practical examples:

  • Before sending a marketing message, verify that the recipient's phone number is active on WhatsApp.
  • Validate user input in a form by checking if the entered phone number exists on WhatsApp.
  • Automate contact list maintenance by filtering out numbers not registered on WhatsApp.

Properties

Name Meaning
Phone Number The phone number to verify, provided in international E.164 format (e.g., +1234567890). Must match the regex pattern /^\+[1-9]\d{1,14}$/.

Output

The node outputs JSON data representing the result of the verification request. The exact structure depends on the response from the Wassenger API but typically includes information indicating whether the phone number exists on WhatsApp.

If the node supports binary data output, it is not relevant for this operation.

Example output JSON might include fields like:

{
  "exists": true,
  "phone": "+1234567890",
  "details": { /* additional info from API */ }
}

Dependencies

  • Requires an API key credential for authenticating with the Wassenger WhatsApp API.
  • The node depends on the Wassenger service being accessible and properly configured.
  • No other external dependencies are indicated.

Troubleshooting

  • Invalid phone number format: If the phone number does not conform to the E.164 format, the node will reject it. Ensure the number starts with "+" followed by country code and subscriber number without spaces or special characters.
  • API authentication errors: If the API key is missing, invalid, or expired, the node will fail to authenticate. Verify the API key configuration.
  • Network or service errors: Connectivity issues or Wassenger service downtime may cause failures. Check network connectivity and service status.
  • Unexpected API responses: If the API changes or returns unexpected data, the node might throw errors. Review the API documentation and update the node accordingly.

Links and References

Discussion