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 basic client information based on a provided client instance ID. It is useful in scenarios where you need to fetch details about a specific client from the WaAPI service, such as for displaying client data in workflows, performing validations, or integrating client info into other processes.
For example, you might use this node to:
- Retrieve and display client details before processing an order.
- Validate client existence and status during automated customer support workflows.
- Synchronize client data between WaAPI and another system.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the client instance whose basic information you want to retrieve. This is a required input. |
Output
The node outputs JSON data containing the basic information of the specified client. The exact structure depends on the WaAPI response but typically includes fields such as client name, contact details, status, and other relevant metadata.
No binary data output is indicated by the source code.
Dependencies
- Requires an active API key credential for the WaAPI service to authenticate requests.
- The node sends HTTP requests to
https://waapi.app/api/v1. - No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing client Id will result in errors or empty responses.
- Authentication failures if the API key credential is not configured correctly.
- Network connectivity problems preventing access to the WaAPI endpoint.
Error messages:
- Unauthorized or 401 errors indicate invalid or missing API credentials; verify your API key configuration.
- 404 Not Found may mean the client Id does not exist; double-check the Id value.
- Timeout or network errors suggest connectivity issues; ensure your server can reach the WaAPI endpoint.
Links and References
- WaAPI Official Documentation (for detailed API usage and client data schema)
- n8n documentation on API Credentials