ZuckZapGo Call icon

ZuckZapGo Call

Manage WhatsApp calls using ZuckZapGo API
Join our community

Overview

This node allows users to manage WhatsApp calls by rejecting incoming calls through the ZuckZapGo API. It is particularly useful in scenarios where automated call handling is needed, such as when a user wants to programmatically decline calls based on certain conditions or during specific times (e.g., outside business hours). For example, a customer support workflow could automatically reject calls with a custom message when agents are unavailable.

Properties

Name Meaning
Call ID The unique identifier of the call to reject.
Call From The JID (Jabber ID) of the caller, typically formatted like a phone number with domain.
Reject Type The type of rejection to send. Options: Busy (line is busy), Declined (call declined), Unavailable (unable to answer).
Custom Message An optional custom text message to send to the caller explaining why the call was rejected.

Output

The node outputs JSON data representing the response from the ZuckZapGo API after attempting to reject the call. This includes details about the rejection status and any messages returned by the API. If an error occurs and "Continue On Fail" is enabled, the output will contain an error object with the error message.

The output structure is an array of JSON objects, each corresponding to an input item processed, containing either the API response or an error description.

Dependencies

  • Requires access to the ZuckZapGo API.
  • Needs an API key credential configured in n8n for authenticating requests to the ZuckZapGo service.
  • The node uses a POST request to the /call/reject/send endpoint of the ZuckZapGo API.

Troubleshooting

  • Common issues:

    • Invalid or missing Call ID or Call From values will cause the API request to fail.
    • Incorrect or expired API credentials will result in authentication errors.
    • Network connectivity problems can prevent the node from reaching the ZuckZapGo API.

  • Error messages:

    • Errors returned from the API will be included in the output if "Continue On Fail" is enabled.
    • Typical error messages might include invalid parameters or authorization failures.

  • Resolution tips:

    • Verify that the Call ID and Call From fields are correctly populated.
    • Ensure the API key credential is valid and has proper permissions.
    • Check network connectivity and firewall settings to allow outbound requests to the API.

Links and References

Discussion