Wuzapi Session icon

Wuzapi Session

Manage WhatsApp sessions in Wuzapi

Actions4

Overview

This node manages WhatsApp sessions using the Wuzapi service. It allows users to perform various session-related operations such as connecting or disconnecting from WhatsApp servers, retrieving QR codes for authentication, checking connection status, pairing a phone number, configuring proxy settings, and managing S3 storage configurations.

The Set Proxy operation specifically enables users to configure proxy settings for their WhatsApp session. This is useful in scenarios where network restrictions require routing traffic through a proxy server, or when users want to enhance privacy by masking their IP address.

Practical examples:

  • Setting up a SOCKS5 proxy with authentication to route WhatsApp traffic securely.
  • Enabling or disabling proxy usage dynamically based on network conditions.

Properties

Name Meaning
Proxy URL The URL of the proxy server to use. Must be in the format http://host:port or socks5://user:pass@host:port.
Enable Proxy Boolean flag to enable (true) or disable (false) the proxy configuration.

Output

The node outputs JSON data representing the response from the Wuzapi API related to proxy configuration. This typically includes confirmation of the proxy settings being applied or any error messages returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Wuzapi API service.
  • Needs an API key credential configured in n8n to authenticate requests to Wuzapi.
  • The node uses HTTP POST requests to the /session/proxy endpoint of the Wuzapi API.

Troubleshooting

  • Common issues:

    • Incorrect proxy URL format can cause the API request to fail. Ensure the URL matches the required pattern (http://host:port or socks5://user:pass@host:port).
    • Network connectivity problems between n8n and the Wuzapi API may prevent setting the proxy.
    • Disabling the proxy while no proxy was previously set might not have any effect but should not cause errors.

  • Error messages:

    • Errors returned from the API will be included in the node's output JSON under an error field if the node is set to continue on failure.
    • Common error messages may relate to authentication failures, invalid proxy URLs, or server-side issues.

  • Resolution tips:

    • Verify the proxy URL syntax carefully.
    • Check that the API key credential is valid and has necessary permissions.
    • Test network connectivity to both the proxy server and the Wuzapi API endpoints.

Links and References

Discussion