Actions30
- Company Actions
- Company (Related) Actions
- Data (Advanced) Actions
- Enrich Actions
- Live Web RAG Actions
- LLM Template Actions
- Other Data Actions
- Validation & Cleansing Actions
Overview
This node integrates with the Bedrijfsdata API to validate global phone numbers. It checks if a given phone number is valid and optionally considers the country context by using an ISO 3166-1 Alpha-2 country code. This validation helps ensure that phone numbers are correctly formatted and potentially reachable, which is useful in data cleansing, contact management, and customer onboarding workflows.
Practical examples:
- Validating user-submitted phone numbers before saving them to a CRM.
- Cleaning up legacy databases by verifying stored phone numbers.
- Ensuring phone numbers conform to country-specific formats during lead generation.
Properties
| Name | Meaning |
|---|---|
| Phone Number | (Required) The phone number string to validate. |
| Country (ISO 3166-1 Alpha-2) | (Optional) Two-letter country code (e.g., "nl" for Netherlands, "us" for United States). Used to provide regional context for validation. |
Output
The node outputs JSON data containing the validation results from the Bedrijfsdata API. The exact structure depends on the API response but typically includes fields indicating whether the phone number is valid, possibly normalized or formatted versions of the number, and additional metadata about the phone number's validity or type.
No binary data output is involved.
Dependencies
- Requires an active connection to the Bedrijfsdata API.
- Requires an API key credential configured in n8n for authentication with the Bedrijfsdata service.
- Network access to
https://api.bedrijfsdata.nl/v1.2must be available.
Troubleshooting
- Invalid or missing phone number: Ensure the "Phone Number" property is provided and correctly formatted as a string.
- Incorrect country code: If validation fails unexpectedly, verify the country code is a valid ISO 3166-1 Alpha-2 code.
- API errors: Common errors may include network issues, invalid API credentials, or rate limiting by the Bedrijfsdata API. Check your API key configuration and network connectivity.
- Unexpected API response: If the node throws errors related to unexpected responses, it might indicate changes in the API or temporary service issues. Review the API status or update the node accordingly.
Links and References
- Bedrijfsdata API Documentation (for detailed API endpoints and parameters)
- ISO 3166-1 Alpha-2 Country Codes