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 send a "presence unavailable" signal for a specific client instance. It is useful in scenarios where you want to programmatically mark a client as offline or unavailable, such as automating presence status updates in messaging or communication applications.
For example, if you manage multiple client instances and need to set their presence to unavailable during maintenance or outside business hours, this node can automate that process by sending the appropriate API request.
Properties
| Name | Meaning |
|---|---|
| Id | The numeric identifier of the client instance for which the presence will be set to unavailable. |
Output
The node outputs JSON data representing the response from the WaAPI API after attempting to send the presence unavailable signal. This typically includes confirmation of the action or any error messages returned by the API.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the WaAPI API.
- The node sends HTTP requests to
https://waapi.app/api/v1. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing client instance ID may cause the API call to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent successful API communication.
Error messages:
- Authentication failures usually indicate invalid API keys; verify and update credentials.
- "Instance not found" or similar errors suggest the provided client ID does not exist; check the ID value.
- Timeout or connection errors imply network issues; ensure stable internet access.
Links and References
- WaAPI Official Documentation (for detailed API usage and presence management)
- n8n HTTP Request Node Documentation (for understanding how API calls are made)