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, setting proxy settings, configuring storage and messaging options, and specifically for this context, configuring how incoming calls are handled (skip calls).
The Configure Skip Calls operation enables users to automatically skip or reject incoming WhatsApp calls with customizable rejection messages and rejection types. This is useful in scenarios where you want to avoid interruptions from calls, for example, when running automated workflows or chatbots that should not be disturbed by voice calls.
Practical examples:
- Automatically reject all incoming calls during business hours with a polite message.
- Set the rejection type to "busy" to indicate the user is currently unavailable.
- Use this configuration to ensure calls do not interfere with message processing workflows.
Properties
| Name | Meaning |
|---|---|
| Enable Skip Calls | Boolean flag to enable or disable automatic skipping/rejecting of incoming calls. |
| Reject Message | Custom message sent to callers when their call is rejected. |
| Reject Type | Type of call rejection; options are: Busy, Declined, Unavailable. |
Output
The node outputs JSON data representing the response from the ZuckZapGo API after performing the requested operation. For the Configure Skip Calls operation, the output typically includes confirmation of the updated skip calls configuration status.
The output structure is an array of JSON objects, each corresponding to an input item processed, containing the API response data.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the ZuckZapGo API via an API key credential configured in n8n.
- The node depends on the ZuckZapGo API endpoints for session management.
- No additional external services are required beyond the API access.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrectly formatted reject message or invalid reject type values may result in API errors.
- Network connectivity problems can prevent successful API requests.
Error messages:
- Authentication errors: Ensure the API key credential is correctly set up and valid.
- Validation errors: Check that the reject message is a string and reject type is one of the allowed options ("busy", "declined", "unavailable").
- Timeout or network errors: Verify internet connectivity and API endpoint availability.
Links and References
- ZuckZapGo API Documentation (replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- WhatsApp Business API official docs for general understanding of call handling (https://developers.facebook.com/docs/whatsapp)