Actions83
- 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 information about a specific phone number instance by its ID. It is useful in scenarios where you need to fetch details of a phone number registered or managed within the WaAPI system, such as verifying number status, metadata, or configuration.
A practical example would be integrating this node into a workflow that manages phone numbers for messaging or calling services, allowing you to programmatically query and confirm number details before proceeding with further actions.
Properties
| Name | Meaning |
|---|---|
| Id | The unique instance ID of the phone number to retrieve. |
| Number | The phone number in international format without leading "+" or "00". Example: 15553334444 |
Output
The node outputs JSON data containing the details of the requested phone number instance. This typically includes all relevant metadata returned by the WaAPI service for that number ID, such as status, configuration, and any other associated attributes.
If the API supports binary data (e.g., images or files related to the number), it would be included in the binary output field, but based on the provided code and properties, the primary output is structured JSON data.
Dependencies
- Requires an active connection to the WaAPI API.
- Needs an API key credential configured in n8n for authentication with the WaAPI service.
- The node uses the base URL
https://waapi.app/api/v1for API requests.
Troubleshooting
- Invalid or missing ID: Ensure the "Id" property is correctly set and corresponds to an existing number instance in WaAPI.
- Incorrect number format: The "Number" must be in international format without leading "+" or "00". Providing an incorrectly formatted number may cause request failures.
- Authentication errors: Verify that the API key credential is properly configured and has sufficient permissions.
- Network issues: Confirm that your environment can reach
https://waapi.app/api/v1. - API rate limits: If you encounter rate limit errors, consider adding delays or upgrading your API plan.