Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Overview
This node interacts with the Wassenger WhatsApp API to manage various resources related to WhatsApp messaging and administration. Specifically, for the Files resource with the Delete File operation, it allows users to delete an outbound file by specifying its unique file ID. This is useful in scenarios where files previously uploaded or sent need to be removed from the system, such as cleaning up outdated media or correcting mistakes.
Practical examples include:
- Deleting a mistakenly uploaded image or document before sending it.
- Removing obsolete marketing materials or campaign attachments.
- Managing storage by deleting files no longer needed.
Properties
| Name | Meaning |
|---|---|
| File ID | The unique identifier of the outbound file to delete. This must be provided as a string. |
Output
The output of this operation is a JSON object representing the result of the delete action. Typically, this will confirm whether the deletion was successful or provide details if it failed. The exact structure depends on the API response but generally includes status information.
No binary data is output by 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 relies on internal methods that handle API calls for outbound files.
Troubleshooting
Common issues:
- Providing an invalid or non-existent File ID will likely cause an error.
- Missing or incorrect API authentication credentials will prevent the operation from succeeding.
- Network connectivity problems can cause timeouts or failures.
Error messages:
- Errors indicating "File not found" suggest the File ID does not exist or has already been deleted.
- Authentication errors indicate issues with the API key; verify the credential setup.
- General API errors should be checked against Wassenger API documentation for specific codes.
To resolve these, ensure the File ID is correct, the API key is valid and active, and network connectivity is stable.
Links and References
- Wassenger API Documentation (for detailed API behavior and error codes)
- n8n Documentation on Creating Custom Nodes