Actions11
Overview
This node manages WhatsApp session connections and configurations via the DinastiAPI service. It allows users to perform various operations such as connecting or disconnecting from WhatsApp servers, logging out devices, pairing phones, configuring proxy settings, and managing media download preferences.
Specifically, the "Configure Skip Media" operation enables or disables skipping the download of media files in the WhatsApp session. This can be useful in scenarios where users want to reduce bandwidth usage or storage by avoiding media downloads, for example, when only text messages are relevant.
Practical examples:
- Automatically skip downloading images and videos in a WhatsApp session to save storage.
- Enable skipping media during high network traffic periods to optimize performance.
Properties
| Name | Meaning |
|---|---|
| Enable Skip Media | Whether to skip downloading media files (true/false) |
Output
The node outputs JSON data representing the response from the DinastiAPI service after performing the requested operation. The output is an array of JSON objects corresponding to each input item processed.
For the "Configure Skip Media" operation, the output typically contains confirmation or status information about the skip media configuration update.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the DinastiAPI service.
- The node makes HTTP requests to DinastiAPI endpoints to manage WhatsApp sessions.
- Proper configuration of the API credentials in n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Network connectivity problems may prevent communication with the DinastiAPI service.
- Incorrect property values (e.g., invalid boolean types) might lead to request errors.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- HTTP 4xx or 5xx errors suggest issues with the request or server; check the parameters and try again.
- If the node fails silently, ensure that the required properties are set correctly and that the DinastiAPI service is reachable.
Links and References
- DinastiAPI Documentation (replace with actual URL if available)
- n8n documentation on Creating Custom Nodes