Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API

Actions148

Overview

This node operation validates and normalizes phone numbers. It is useful when you need to ensure that phone numbers conform to international or country-specific formats before using them in communications, databases, or integrations. For example, it can be used to clean up user-submitted phone numbers on a website, verify contact lists before sending messages, or standardize phone number formats for CRM imports.

Properties

Name Meaning
Country The country code to validate the phone numbers against. Options include all countries (e.g., "United States", "Germany", "India") or "Any country" for no specific country validation.
Phone Numbers A list of phone numbers to validate and normalize. Each entry requires a phone number string input.

Output

The output JSON contains the results of validating each provided phone number. Each item corresponds to one input phone number and includes information about its validity and normalized format. This allows downstream nodes or workflows to use clean, validated phone numbers or handle invalid entries accordingly.

If the node supports binary data output, it would typically relate to raw data or files, but this operation focuses on JSON validation results only.

Dependencies

  • Requires an API key credential for authentication with the Wassenger WhatsApp API service.
  • The node depends on the external Wassenger API to perform phone number validation and normalization.
  • No additional environment variables are explicitly required beyond the API key configuration.

Troubleshooting

  • Invalid API Key or Authentication Errors: Ensure the API key credential is correctly configured and active.
  • Invalid Phone Number Format: If phone numbers do not validate, check that they are entered correctly and optionally specify the correct country code to improve validation accuracy.
  • Empty or Missing Phone Numbers: The node requires at least one phone number to validate; ensure the input collection is not empty.
  • API Rate Limits or Connectivity Issues: Network problems or API rate limits may cause errors; retry or check API usage quotas.

Links and References

Discussion