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 retrieve details about files associated with WhatsApp chats. Specifically, the "Get File Details" operation under the "Chat Files" resource fetches metadata and information about a particular file sent or received via a specified WhatsApp number.
Common scenarios where this node is beneficial include:
- Retrieving detailed information about media files (images, videos, documents) exchanged in WhatsApp conversations for auditing or processing.
- Integrating WhatsApp file metadata into CRM or support systems to track attachments.
- Automating workflows that require validation or logging of files shared over WhatsApp.
For example, a user might use this node to get the size, type, or timestamp of a file sent by a customer to decide whether to download or process it further.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) from which the file was sent or received. |
| File ID | The unique identifier of the file whose details are to be retrieved. |
- WhatsApp Number: This property expects a string representing the device ID of the WhatsApp number. It supports loading options dynamically to select from available devices.
- File ID: This property expects a string representing the file's unique ID. It also supports dynamic loading of available files for selection.
Output
The node outputs JSON data containing the details of the requested file. This typically includes metadata such as file name, size, MIME type, timestamps, and possibly URLs or identifiers needed to access or download the file.
If the node supports binary data output (not explicitly shown in the provided code), it would represent the actual file content in the binary field, allowing downstream nodes to handle or save the file.
Dependencies
- Requires an active connection to the Wassenger WhatsApp API using a valid API key credential.
- The node depends on the Wassenger API endpoints related to chat files.
- Proper configuration of the API key credential within n8n is necessary for authentication.
Troubleshooting
Common issues:
- Invalid or expired API key leading to authentication errors.
- Incorrect WhatsApp Number or File ID causing "file not found" or similar errors.
- Network connectivity problems preventing API calls.
Error messages:
- Errors returned from the API will be surfaced in the node output if "Continue On Fail" is enabled.
- Typical error messages may include authorization failures, invalid parameters, or resource not found.
Resolutions:
- Verify the API key credential is correctly set and has required permissions.
- Confirm the WhatsApp Number and File ID values are correct and exist.
- Check network connectivity and API endpoint availability.
Links and References
- Wassenger Official API Documentation (for detailed API usage and file operations)
- n8n Documentation (for general guidance on using credentials and handling node errors)