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 perform operations related to WhatsApp clients. Specifically, the "Logout" operation for the "Client" resource logs out a client instance identified by its ID. This is useful in scenarios where you want to programmatically terminate a WhatsApp client session, for example, to force logout a user or reset the client state.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID of the WhatsApp client to log out. This is a required numeric identifier specifying which client session to terminate. |
Output
The node outputs JSON data representing the result of the logout operation. Typically, this would include confirmation of the logout action or any relevant status messages returned by the WaAPI API. The output does not explicitly mention binary data, so it is assumed to be purely JSON.
Dependencies
- Requires an API key credential for authenticating with the WaAPI API.
- The node uses the base URL
https://waapi.app/api/v1for all requests. - It depends on the external service WaAPI, which provides WhatsApp client management via REST API.
Troubleshooting
- Common issues:
- Invalid or missing instance ID will cause the logout request to fail.
- Authentication errors if the API key credential is incorrect or expired.
- Network connectivity problems preventing access to the WaAPI endpoint.
- Error messages:
- Unauthorized or 401 errors indicate issues with API authentication; verify the API key.
- 404 errors may mean the specified client ID does not exist.
- Timeout or connection errors suggest network issues or API downtime.
Links and References
- WaAPI Official Documentation (for detailed API usage and client management)
- n8n documentation on creating custom nodes