Wassenger icon

Wassenger

Interact with Wassenger WhatsApp API

Actions148

Overview

This node integrates with the Wassenger WhatsApp API to manage WhatsApp chats and related data. Specifically, the "Delete Chat Note" operation under the "Chats" resource allows users to delete one or more notes associated with a particular WhatsApp chat. This is useful for cleaning up or managing metadata attached to chats, such as removing outdated or irrelevant notes.

Practical scenarios include:

  • Automatically deleting notes after a certain workflow step completes.
  • Removing sensitive or temporary notes from chats.
  • Managing chat annotations in bulk by specifying multiple note IDs.

Properties

Name Meaning
WhatsApp Number The ID of the WhatsApp number (device) from which the chat belongs.
Chat ID The unique identifier of the chat where notes will be deleted. Examples: user or group chat IDs.
Note IDs One or more IDs of the notes to delete from the specified chat.

Output

The output JSON contains the response from the Wassenger API after attempting to delete the specified chat notes. It typically includes confirmation of deletion or error details if the operation failed.

No binary data is output by this operation.

Dependencies

  • Requires an active Wassenger WhatsApp API key credential configured in n8n.
  • The node depends on the Wassenger API being accessible and the provided WhatsApp number and chat IDs being valid within that account.

Troubleshooting

  • Invalid Chat ID: If the chat ID does not exist or is malformed, the API may return an error. Verify the chat ID format (e.g., 447362053576@c.us for users, 44736205357600000000@g.us for groups).
  • Note IDs Not Found: Attempting to delete non-existent note IDs will likely cause errors. Ensure the note IDs are correct and belong to the specified chat.
  • Authentication Errors: Missing or invalid API key credentials will prevent the operation from succeeding.
  • Permission Issues: The WhatsApp number used must have access rights to the chat and its notes.
  • To handle errors gracefully, enable "Continue On Fail" in the node settings to capture error messages in the output JSON.

Links and References

Discussion