Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API

Actions148

Overview

This node integrates with the Wassenger WhatsApp API, providing various operations related to WhatsApp messaging and management. Specifically, for the Webhooks resource, it supports operations such as deleting a webhook.

The Delete Webhook operation allows users to remove an existing webhook by specifying its unique ID. This is useful in scenarios where you want to stop receiving event notifications from a particular webhook or clean up unused webhooks to maintain system hygiene.

Practical example:
If you have set up a webhook to listen for incoming WhatsApp messages but no longer need it (e.g., after a campaign ends), you can use this operation to delete that webhook by providing its ID, ensuring that your system no longer receives those events.

Properties

Name Meaning
Webhook ID The unique identifier of the webhook to delete

Output

The output of the Delete Webhook operation is a JSON object representing the response from the Wassenger API after attempting to delete the specified webhook. Typically, this will include confirmation of deletion or relevant status information.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Wassenger WhatsApp API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • The node depends on the executeWebhookOperations method from the bundled source code to perform webhook-related actions.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Webhook ID will likely result in an error indicating that the webhook could not be found.
    • Missing or incorrect API authentication credentials will cause authorization failures.
    • Network connectivity problems may prevent successful communication with the Wassenger API.
  • Error messages and resolutions:

    • "Webhook not found": Verify that the Webhook ID is correct and that the webhook exists.
    • "Unauthorized" or similar authentication errors: Check that the API key credential is correctly set up and valid.
    • Timeout or network errors: Ensure stable internet connection and that the Wassenger API endpoint is reachable.

Links and References

Discussion