Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Other → Validate phone numbers
AI-generatedOverview
This node validates and normalizes phone numbers, optionally restricting validation to a specific country. It is useful in workflows where you need to ensure that phone numbers are correctly formatted and valid before further processing, such as sending messages, importing contacts, or integrating with communication platforms.
For example, you might use this node to:
- Validate a list of customer phone numbers before adding them to a marketing campaign.
- Normalize phone numbers from various sources into a consistent format.
- Filter out invalid phone numbers to reduce errors in downstream systems.
Properties
| Name | Meaning |
|---|---|
| Country | The country code to validate the phone numbers against. Options include all countries plus "Any country" for no restriction. |
| Phone Numbers | A collection of one or more phone numbers to validate. Each entry requires a phone number string (max length 50). |
Output
The node outputs an array of JSON objects, each corresponding to a validated phone number. Each output item contains the validation result and normalized phone number data. The exact structure depends on the underlying validation logic but typically includes fields indicating whether the number is valid, its normalized form, and possibly additional metadata like country or type.
No binary data output is produced by this node.
Dependencies
- This node relies on an internal phone number validation method provided by the bundled
otheraction module. - No external API keys or credentials are required specifically for this operation beyond the general API key credential needed by the overall node integration.
Troubleshooting
- Invalid phone numbers: If phone numbers are not recognized as valid, verify that the input format matches expected international or national formats. Also, check if the correct country code is selected or leave it empty to allow any country.
- Empty or missing phone numbers: Ensure that the phone numbers property is populated with valid strings; empty inputs will cause validation to fail.
- Error messages: Errors thrown during execution typically relate to invalid input types or exceeding maximum allowed lengths. Correct the input accordingly.
- Continue on Fail: If enabled, the node will continue processing remaining numbers even if some fail validation, returning error details per failed item.
Links and References
- E.164 International Phone Number Formatting
- libphonenumber - Google's phone number handling library (commonly used for phone validation and formatting)