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 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 systems.
For example, you might use this node to:
- Retrieve and display client details before processing an order.
- Validate client existence and status during automated workflows.
- Synchronize client data between WaAPI and another CRM system.
Properties
| Name | Meaning |
|---|---|
| Id | The unique instance ID of the client whose basic information you want to retrieve. This is a required numeric input. |
Output
The node outputs JSON data containing the basic information of the specified client retrieved from the WaAPI API. The exact structure depends on the API response but typically includes client attributes such as name, contact details, status, and other relevant metadata.
No binary data output is expected from this operation.
Dependencies
- Requires an active API key credential for authenticating with the WaAPI API.
- The node uses the base URL
https://waapi.app/api/v1to make requests. - Proper configuration of the API authentication credentials within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing client ID will result in errors or empty responses.
- Authentication failures due to incorrect or expired API keys.
- Network connectivity problems preventing access to the WaAPI endpoint.
Error messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly set up and valid.
- "Client not found": Verify that the provided client ID exists in the WaAPI system.
- Timeouts or network errors: Ensure your server can reach
https://waapi.app/api/v1.
Resolving these usually involves verifying input parameters, refreshing credentials, and checking network settings.
Links and References
- WaAPI Official Documentation (for detailed API endpoints and data structures)
- n8n Documentation on Credentials (for setting up API authentication)