Actions11
Overview
This node manages WhatsApp session connections and configurations via the DinastiAPI service. It supports various operations such as connecting, disconnecting, logging out, pairing a phone, setting proxy settings, and configuring integrations like S3 storage and RabbitMQ messaging. The "Set Proxy" operation specifically allows users to enable or disable a proxy and specify the proxy URL for routing WhatsApp session traffic through a proxy server.
Practical scenarios include:
- Using a proxy server to route WhatsApp session traffic for privacy, security, or network routing reasons.
- Managing WhatsApp session lifecycle events programmatically.
- Configuring external services (S3, RabbitMQ) to handle media storage or event messaging related to WhatsApp sessions.
Example use case for "Set Proxy":
- A user wants to route WhatsApp connection traffic through a SOCKS5 proxy with authentication to comply with corporate network policies.
Properties
| Name | Meaning |
|---|---|
| Proxy Configuration | Collection of proxy settings: |
| - Enable Proxy | Boolean flag to enable or disable the proxy usage. |
| - Proxy URL | The proxy server URL in format protocol://[user:pass@]host:port, e.g., socks5://user:pass@host:port or http://host:port. Only shown if proxy is enabled. |
Output
The node outputs JSON data representing the response from the DinastiAPI endpoint corresponding to the "Set Proxy" operation. This typically includes confirmation of the proxy configuration update or error details if the operation failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the DinastiAPI service.
- The node makes HTTP requests to DinastiAPI endpoints to perform session management actions.
- No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
Common issues:
- Invalid proxy URL format may cause the API request to fail.
- Enabling proxy without specifying a valid proxy URL will likely result in an error.
- Network connectivity issues between n8n and the DinastiAPI service can cause timeouts or failures.
Error messages:
- Errors returned from the API will be caught and handled; typical messages might indicate invalid parameters or authentication failures.
- If the proxy URL is malformed, expect validation errors from the API.
Resolution tips:
- Ensure the proxy URL follows the correct format including protocol and port.
- Verify that the API key credential is correctly configured and has necessary permissions.
- Test network connectivity to the proxy server independently before configuring it here.
Links and References
- DinastiAPI Documentation (for detailed API usage and proxy configuration)
- Proxy URL Format Reference