Actions31
- 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 perform phone number validation as part of its "Validation & Cleansing" resource. Specifically, the "Validate Phone Number" operation allows users to verify and validate global phone numbers, optionally specifying a country code to improve accuracy.
Common scenarios for this node include:
- Ensuring user-submitted phone numbers are valid before storing or using them.
- Cleaning up contact lists by validating phone numbers in bulk.
- Integrating phone validation into workflows that require verified contact information, such as CRM updates or marketing automation.
For example, a workflow could take a list of customer phone numbers, pass each through this node to validate and format them according to their respective countries, and then proceed only with the validated contacts.
Properties
| Name | Meaning |
|---|---|
Phone Number (phone) |
(Required) The phone number string to validate. |
Country (ISO 3166-1 Alpha-2) (country_code) |
(Optional) Two-letter country code (e.g., "nl", "us") to specify the phone number's country context for more accurate validation. Defaults to "nl". |
Output
The node outputs JSON data containing the validation results from the Bedrijfsdata API. This typically includes whether the phone number is valid, possibly formatted versions of the number, and additional metadata related to the phone number's validity and type.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Bedrijfsdata API.
- Requires an API key credential configured in n8n for authenticating requests to the Bedrijfsdata service.
- Network access to
https://api.bedrijfsdata.nl/v1.2is necessary.
Troubleshooting
- Invalid or missing phone number: If the phone number input is empty or malformed, the API may return an error or invalid response. Ensure the phone number is provided and correctly formatted as a string.
- Incorrect country code: Providing an incorrect or unsupported country code may lead to inaccurate validation results. Use valid ISO 3166-1 alpha-2 codes.
- API authentication errors: If the API key credential is missing, expired, or invalid, the node will fail to authenticate. Verify the API key configuration in n8n.
- Network issues: Connectivity problems to the Bedrijfsdata API endpoint can cause request failures. Check network settings and firewall rules.
- Unexpected API responses: In rare cases, the API might return unexpected data or errors. Review the error messages returned by the node for clues and consult Bedrijfsdata API documentation or support.
Links and References
- Bedrijfsdata API Documentation (general reference for API endpoints and parameters)
- ISO 3166-1 Alpha-2 Country Codes (for valid country codes)
Note: This summary is based on static analysis of the node's source code and property definitions without runtime execution.