Actions85
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node interacts with the WaAPI API to retrieve the country code associated with a given phone number. It is useful in scenarios where you need to identify the country origin of phone numbers, such as validating user input, formatting phone numbers for international use, or enriching contact data with geographic information.
For example, if you have a list of phone numbers and want to automatically determine their country codes for routing calls or sending localized messages, this node can automate that process by querying the WaAPI service.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (a numeric identifier for the instance) |
| Number | Phone number to get country code for |
Output
The node outputs JSON data containing the response from the WaAPI API about the phone number's country code. The exact structure depends on the API response but typically includes fields such as the detected country code, country name, and possibly additional metadata related to the phone number.
No binary data output is indicated.
Dependencies
- Requires an active connection to the WaAPI API service at
https://waapi.app/api/v1. - Requires an API key credential for authentication with the WaAPI API.
- The node uses HTTP requests with JSON payloads and expects JSON responses.
- No other external dependencies are indicated.
Troubleshooting
- Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Providing improperly formatted phone numbers may result in errors or no country code found.
- Network connectivity issues can prevent successful API calls.
- Error messages:
- Authentication errors typically indicate invalid credentials; verify the API key setup.
- Validation errors may occur if the "Number" property is empty or malformed; ensure it is a valid phone number string.
- Timeout or network errors suggest connectivity problems; check your internet connection and API availability.
Links and References
- WaAPI Official Website
- WaAPI API Documentation (for details on request/response formats and usage)