ZuckZapGo Webhook icon

ZuckZapGo Webhook

Configure webhooks for ZuckZapGo WhatsApp API
Join our community

Actions2

Overview

This node allows you to manage webhook configurations for the ZuckZapGo WhatsApp API. It supports operations to set, get, update, or delete webhook settings. Webhooks enable real-time event notifications from the WhatsApp API to your specified URL, making it useful for integrating WhatsApp messaging events into your workflows.

Common scenarios include:

  • Setting up a webhook URL to receive incoming WhatsApp messages and presence updates.
  • Subscribing to specific event types such as message delivery receipts or chat presence.
  • Updating existing webhook configurations without removing them.
  • Removing webhook configurations when no longer needed.

Practical example:
You want to receive notifications whenever a new WhatsApp message arrives or when a user changes their online status. You configure the webhook URL and subscribe to "Message" and "Presence" events using this node's "Set" operation.

Properties

Name Meaning
Webhook URL The URL that will receive webhook events.
Events Event types to subscribe to. Options: All, Chat Presence, History Sync, Media Retry, Message, Presence, Read Receipt, Receipt.

Output

The node outputs JSON data representing the response from the ZuckZapGo API regarding webhook configuration. This includes details of the current webhook setup after performing the requested operation (get, set, update, or delete).

If an error occurs during execution, the output JSON will contain an error field with the error message.

No binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the ZuckZapGo WhatsApp API.
  • The node uses HTTP requests to the /webhook endpoint of the ZuckZapGo API.
  • Proper network access to the ZuckZapGo API and the configured webhook URL is necessary.

Troubleshooting

  • Invalid Webhook URL: Ensure the webhook URL is a valid HTTPS endpoint accessible from the internet.
  • Subscription Errors: Selecting invalid or unsupported event types may cause errors; use only the provided event options.
  • API Authentication Failures: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Network Issues: Connectivity problems between n8n and the ZuckZapGo API or the webhook URL can cause failures.
  • Error Messages: If the node returns an error in the output JSON, check the message for clues (e.g., authentication failure, invalid parameters) and adjust accordingly.

Links and References

Discussion