ZuckZapGo Session icon

ZuckZapGo Session

Manage WhatsApp session connections and configurations

Overview

This node manages WhatsApp session connections and configurations via the ZuckZapGo service API. It allows users to perform various session-related operations such as connecting, disconnecting, logging out, pairing a phone, setting proxies, configuring storage and messaging options, and specifically for this context, configuring whether to skip processing broadcast messages.

A practical use case for the "Configure Skip Broadcasts" operation is when you want to control if broadcast messages received by the WhatsApp session should be processed or ignored. This can help reduce noise in workflows that only need direct messages or other types of events.

Properties

Name Meaning
Enable Skip Broadcasts Whether to skip processing broadcast messages (true/false)

Output

The node outputs JSON data representing the response from the ZuckZapGo API after performing the requested operation. The output is an array of JSON objects, each corresponding to an input item processed.

For the "Configure Skip Broadcasts" operation, the output typically contains confirmation or status information about the updated skip broadcasts configuration.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the ZuckZapGo WhatsApp session management API.
  • The node makes HTTP requests to various endpoints under /session/... to perform operations.
  • No additional external services are required beyond the configured API access.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect property values (e.g., invalid boolean types) may result in request errors.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • Errors returned from the API will be caught and handled by the node, typically indicating the nature of the failure (e.g., unauthorized, bad request).
    • If the node fails silently, verify that the API key credential is correctly set up and has necessary permissions.
    • For proxy or network-related errors, ensure the proxy settings and network environment allow outbound connections to the API endpoint.

Links and References

Discussion