Actions20
- Session Actions
- Message Actions
- Contact Actions
- Typing Actions
- Webhook Actions
Overview
The "Download Image" operation of the WhatsApp Multi-Session node allows users to retrieve images sent in messages via the WhatsApp API. This functionality is particularly useful for applications that need to process or store media content received from users, such as chatbots, customer support systems, or any service that interacts with WhatsApp messages. For example, a business could use this node to automatically download and archive images sent by customers for record-keeping or analysis.
Properties
| Name | Meaning |
|---|---|
| Session ID | The WhatsApp session ID required to authenticate the request. |
| Phone Number | The recipient's phone number (including country code, without the '+' sign). |
| Media URL | The temporary media URL from which the image will be downloaded. |
| Output Format | The format in which the downloaded image data will be returned: Base64, Binary, or File. |
| Put Output File in Field | The name of the binary property where the file will be written if the output format is set to File. |
Output
The output structure of the json field varies based on the selected output format:
- Base64: Returns an object containing the success status, a message indicating successful download, the base64 encoded image data, its size, MIME type, and filename.
- Binary: Similar to Base64 but returns the image data as a binary buffer instead.
- File: Provides a similar structure as Base64 but includes a binary property containing the file data, MIME type, and filename.
If the node encounters errors during the download process, it will return an error object detailing the issue, including an error message and any relevant details.
Dependencies
- An API key credential is required to authenticate requests to the WhatsApp Multi-Session API.
- The node must be configured with the server URL of the WhatsApp Multi-Session API.
Troubleshooting
Common issues users might encounter include:
- Expired Media Link: If the media URL has expired, the node will return an error indicating that a new media URL must be requested.
- Media File Not Found: If the specified media file does not exist, the node will indicate that the file could not be found.
- Authentication Failed: If the API key is invalid or permissions are insufficient, the node will throw an authentication error.
- Access Forbidden: Users may receive an access forbidden error if they do not have permission to access the media file.
To resolve these issues, ensure that the media URL is valid and has not expired, verify the API key and permissions, and check the server settings.