Actions11
Overview
This node manages WhatsApp session connections and configurations via the ZuckZapGo API. It allows users to perform various session-related operations such as connecting, disconnecting, logging out, pairing a phone number, configuring proxy settings, and managing skip message filters.
The "Configure Skip Own Messages" operation specifically enables or disables skipping the processing of messages sent by the user themselves. This can be useful in scenarios where you want to avoid handling or reacting to your own outgoing messages within an automation workflow, reducing noise or preventing loops.
Practical example:
If you have an automation that listens for incoming WhatsApp messages to trigger certain actions, enabling "Skip Own Messages" ensures that messages you send from the same account do not trigger those automations.
Properties
| Name | Meaning |
|---|---|
| Enable Skip Own Messages | Boolean flag to enable or disable skipping the processing of your own sent messages. |
Output
- The node outputs JSON data representing the response from the ZuckZapGo API for the requested operation.
- For the "Configure Skip Own Messages" operation, the output will typically confirm the updated configuration status (enabled or disabled).
- The output is structured as an array of JSON objects, each corresponding to an input item processed.
- No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the ZuckZapGo API.
- The node depends on the external ZuckZapGo service to manage WhatsApp sessions.
- Proper network connectivity to the ZuckZapGo API endpoints is necessary.
- No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Network connectivity problems may prevent successful API requests.
- Incorrect property values (e.g., non-boolean for enabling skip) might cause request errors.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- HTTP errors from the API (e.g., 400 or 500 status codes) suggest malformed requests or server issues; check property values and retry later.
- If the node fails silently, ensure the correct operation ("configureSkipOwnMessages") is selected and the boolean property is set properly.
Links and References
- ZuckZapGo API Documentation (replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- WhatsApp Business API general info: https://developers.facebook.com/docs/whatsapp
Note: This summary focuses solely on the "Configure Skip Own Messages" operation of the node as requested.